bgpreport

Network · data from 2026-11-12

AS10540 InfoDOOR Pty Ltd - InfoDOOR Pty Ltd

Registry name: InfoDOOR Pty Ltd - InfoDOOR Pty Ltd, ZA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10540, 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.
86.106.128.0/24 Invalid: origin Other origin only 4 1%low visibility 2
58.145.180.0/22 No ROA Other IRR onlyRADB 670 100% 67
202.6.8.0/22 No ROA Other IRR onlyRADB 670 100% 67
202.47.8.0/22 No ROA Other IRR onlyRADB 670 100% 67
58.145.176.0/23 No ROA Other IRR onlyRADB 3 0%low visibility 3
202.6.14.0/23 No ROA Other IRR onlyRADB 3 0%low visibility 3
202.47.14.0/23 No ROA Other IRR onlyRADB 3 0%low visibility 3

AS-SET

AS10540 isn't in PeeringDB, where networks name their 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 14 are in fix.csv.

  • ROA: origin1
  • ROA: none6
  • Route object: none1
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: origin86.106.128.0/24ROAs covering it name AS64441, not AS10540. If AS10540 should announce it, add a ROA for AS10540.4 of 673
Route object: none86.106.128.0/24Route objects for it name AS64441. Add a route object with origin AS10540 in the RIR database for the space.4 of 673
ROA: none58.145.180.0/22No ROA covers it. Add a ROA for AS10540, maxLength 22.670 of 673
Route object: RIR58.145.180.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none202.6.8.0/22No ROA covers it. Add a ROA for AS10540, maxLength 22.670 of 673
Route object: RIR202.6.8.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none202.47.8.0/22No ROA covers it. Add a ROA for AS10540, maxLength 22.670 of 673
Route object: RIR202.47.8.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none58.145.176.0/23No ROA covers it. Add a ROA for AS10540, maxLength 23.3 of 673
Route object: RIR58.145.176.0/23Route object only in RADB. Add it in the RIR database for the space.3 of 673
ROA: none202.6.14.0/23No ROA covers it. Add a ROA for AS10540, maxLength 23.3 of 673
Route object: RIR202.6.14.0/23Route object only in RADB. Add it in the RIR database for the space.3 of 673
ROA: none202.47.14.0/23No ROA covers it. Add a ROA for AS10540, maxLength 23.3 of 673
Route object: RIR202.47.14.0/23Route object only in RADB. Add it in the RIR database for the space.3 of 673

Route objects not announced

Every route object with origin AS10540 is announced.

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.