bgpreport

Network · data from 2026-11-12

AS58982 DATAPIPE-SG-AP - DataPipe

Registry name: DATAPIPE-SG-AP - DataPipe, SG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS58982, 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.
103.251.196.0/23 No ROA Other IRR onlyRADB 673 100% 67
103.254.44.0/22 No ROA Other IRR onlyRADB 673 100% 67
147.75.28.0/22 No ROA Other IRR onlyRADB 673 100% 67
192.68.41.0/24 No ROA Other IRR onlyRADB 673 100% 67
203.60.128.0/19 No ROA Other IRR onlyRADB 673 100% 67
203.60.144.0/20 No ROA Other IRR onlyRADB 673 100% 67
203.60.144.0/24 No ROA Other IRR onlyRADB 673 100% 67
2407:bd00::/32 No ROA RIR databaseAPNIC, RADB 636 100% 68

AS-SET

AS58982 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 17 are in fix.csv.

  • ROA: none8
  • Route object: RIR7
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none103.251.196.0/23No ROA covers it. Add a ROA for AS58982, maxLength 23.673 of 673
Route object: RIR103.251.196.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.254.44.0/22No ROA covers it. Add a ROA for AS58982, maxLength 22.673 of 673
Route object: RIR103.254.44.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none147.75.28.0/22No ROA covers it. Add a ROA for AS58982, maxLength 22.673 of 673
Route object: RIR147.75.28.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.68.41.0/24No ROA covers it. Add a ROA for AS58982, maxLength 24.673 of 673
Route object: RIR192.68.41.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.60.128.0/19No ROA covers it. Add a ROA for AS58982, maxLength 19.673 of 673
Route object: RIR203.60.128.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.60.144.0/20No ROA covers it. Add a ROA for AS58982, maxLength 20.673 of 673
Route object: RIR203.60.144.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.60.144.0/24No ROA covers it. Add a ROA for AS58982, maxLength 24.673 of 673
Route object: RIR203.60.144.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2407:bd00::/32No ROA covers it. Add a ROA for AS58982, maxLength 32.636 of 636

Route objects not announced

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

156.53.53.0/24RADBNo ROA
2407:fa00::/32RADBNo 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.