bgpreport

Network · data from 2026-11-12

AS209557 GEELINX

Registry name: GEELINX-AS GEELINX LTD, GB · PeeringDB

3IPv4 routes 0.0% RPKI valid · 0.0% with a route object
4IPv6 routes 75.0% RPKI valid · 50.0% with a route object
4RPKI invalid 4 origin · 0 maxLength
0No ROA 5 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS209557, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS209557, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
109.66.88.0/23 Invalid: origin Other origin only 7 1%low visibility 6
109.66.88.0/24 Invalid: origin None 7 1%low visibility 7
109.66.89.0/24 Invalid: origin None 7 1%low visibility 7
2a12:cb40::/48 Invalid: origin RIR databaseRIPE 1 0%low visibility 1
2a0f:1cc6:b121::/48 Valid None 635 100% 69
2a0f:1cc6:b122::/48 Valid None 635 100% 69
2a0f:1cc6:b120::/48 Valid RIR databaseRIPE 635 100% 70

AS-SET

AS209557's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 15 are in fix.csv.

  • ROA: origin4
  • Route object: none5
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: origin109.66.88.0/23ROAs covering it name AS135542, AS136038, not AS209557. If AS209557 should announce it, add a ROA for AS209557.7 of 673
Route object: none109.66.88.0/23Route objects for it name AS135542, AS136038. Add a route object with origin AS209557 in the RIR database for the space.7 of 673
ROA: origin109.66.88.0/24ROAs covering it name AS135542, AS136038, not AS209557. If AS209557 should announce it, add a ROA for AS209557.7 of 673
Route object: none109.66.88.0/24No route object for it. Add a route object with origin AS209557 in the RIR database for the space.7 of 673
ROA: origin109.66.89.0/24ROAs covering it name AS135542, AS136038, not AS209557. If AS209557 should announce it, add a ROA for AS209557.7 of 673
Route object: none109.66.89.0/24No route object for it. Add a route object with origin AS209557 in the RIR database for the space.7 of 673
ROA: origin2a12:cb40::/48ROAs covering it name AS10977, AS199605, AS215172, not AS209557. If AS209557 should announce it, add a ROA for AS209557.1 of 636
Route object: none2a0f:1cc6:b121::/48No route object for it. Add a route object with origin AS209557 in the RIR database for the space.635 of 636
Route object: none2a0f:1cc6:b122::/48No route object for it. Add a route object with origin AS209557 in the RIR database for the space.635 of 636

Route objects not announced

Route objects with origin AS209557 whose prefix no peer sees AS209557 announce. Many are kept on purpose (backup routes, space announced only in some places).

102.165.41.0/24AFRINICInvalid: origin
154.16.16.0/24AFRINICInvalid: origin
2405:a640:1173::/48APNICValid
2406:8dc0:2203::/48ALTDBNo ROA
2602:feda:b88::/47ARINNo ROA
2602:feda:cb0::/44ARINNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.