bgpreport

Network · data from 2026-11-12

AS56094 ITENET-SG - ITENET:wq

Registry name: ITENET-SG - ITENET:wq, SG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56094, 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.
2403:6d00::/32 No ROA Other IRR onlyRADB 636 100% 69
2403:6d00::/36 No ROA Other IRR onlyRADB 636 100% 69
2403:6d00:cc::/48 No ROA Other IRR onlyRADB 636 100% 69
2403:6d00:ce::/48 No ROA Other IRR onlyRADB 636 100% 69
2403:6d00:1000::/36 No ROA Other IRR onlyRADB 636 100% 69
45.127.168.0/22 Valid RIR databaseAPNIC 671 100% 67
103.196.112.0/24 Valid RIR databaseAPNIC 671 100% 67
103.196.113.0/24 Valid RIR databaseAPNIC 671 100% 67
103.196.115.0/24 Valid RIR databaseAPNIC 671 100% 67
182.54.228.0/24 Valid RIR databaseAPNIC 671 100% 67
182.54.229.0/24 Valid RIR databaseAPNIC 671 100% 67
182.54.230.0/24 Valid RIR databaseAPNIC 671 100% 67
182.54.231.0/24 Valid RIR databaseAPNIC 671 100% 67
103.196.114.0/24 Valid RIR databaseAPNIC 670 100% 67

AS-SET

AS56094 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 22 are in fix.csv.

  • ROA: none5
  • Route object: RIR5
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none2403:6d00::/32No ROA covers it. Add a ROA for AS56094, maxLength 32.636 of 636
Route object: RIR2403:6d00::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2403:6d00::/36No ROA covers it. Add a ROA for AS56094, maxLength 36.636 of 636
Route object: RIR2403:6d00::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2403:6d00:cc::/48No ROA covers it. Add a ROA for AS56094, maxLength 48.636 of 636
Route object: RIR2403:6d00:cc::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2403:6d00:ce::/48No ROA covers it. Add a ROA for AS56094, maxLength 48.636 of 636
Route object: RIR2403:6d00:ce::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2403:6d00:1000::/36No ROA covers it. Add a ROA for AS56094, maxLength 36.636 of 636
Route object: RIR2403:6d00:1000::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

45.127.168.0/23APNICValid
45.127.168.0/24APNICValid
45.127.169.0/24APNICValid
45.127.170.0/23APNICValid
45.127.170.0/24APNICValid
45.127.171.0/24APNICValid
103.196.112.0/22APNICValid
103.196.112.0/23APNICValid
103.196.114.0/23APNICValid
182.54.228.0/22APNICValid
182.54.228.0/23APNICValid
182.54.230.0/23APNICValid

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.