BGP Tickets created without remote_addr

[runborg]

In some instances i see tickets are created without the remote_addr field.
The origin of this issue is unknown.
Example ticket from zino-state.json

"11459": {
  "id": 11459,
  "router": "XXXXXX",
  "type": "bgp",
  "state": "open",
  "opened": "2024-08-22T15:44:57.817240Z",
  "updated": "2024-09-03T22:51:39.680282Z",
  "priority": 100,
  "lastevent": "peer was reset (now up)",
  "log": [
    {
      "timestamp": "2024-08-22T15:44:57.817228Z",
      "message": "XXXXX AS 64696 is down (running)"
    },
    {
      "timestamp": "2024-08-22T18:06:19.486323Z",
      "message": "XXXXXX AS 64696 was reset (now up)"
    },
    {
      "timestamp": "2024-09-03T22:08:02.563404Z",
      "message": "XXXXXX  AS 64696 is down (running)"
    },
    {
      "timestamp": "2024-09-03T22:16:23.918023Z",
      "message": "XXXXXX  AS 64696 was reset (now up)"
    },
    {
      "timestamp": "2024-09-03T22:42:51.731228Z",
      "message": "XXXXXX  AS 64696 is down (running)"
    },
    {
      "timestamp": "2024-09-03T22:51:39.680282Z",
      "message": "XXXXXX  AS 64696 was reset (now up)"
    }
  ],
  "history": [
    {
      "timestamp": "2024-08-22T15:44:57.817245Z",
      "message": "state change embryonic -> open (monitor)"
    }
  ],
  "polladdr": "xxxxxx",
  "remote_as": 64696,
  "peer_uptime": 311,
  "operational_state": "established",
  "admin_status": "running"
},