bgpreport

Network · data from 2026-11-12

AS133551 ORIGINNET-AS-AP - OriginNet

Registry name: ORIGINNET-AS-AP - OriginNet, PK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS133551, 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.54.148.0/24 Valid Other IRR onlyRADB 673 100% 67
103.54.149.0/24 Valid Other IRR onlyRADB 673 100% 67
103.54.150.0/24 Valid Other IRR onlyRADB 673 100% 67
103.54.151.0/24 Valid Other IRR onlyRADB 673 100% 67
103.48.0.0/24 Valid RIR databaseAPNIC 673 100% 66
103.48.1.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.209.76.0/24 Valid RIR databaseAPNIC 673 100% 67
103.209.79.0/24 Valid RIR databaseAPNIC 673 100% 67
160.30.108.0/24 Valid RIR databaseAPNIC 673 100% 66
165.99.254.0/24 Valid RIR databaseAPNIC 673 100% 66
165.99.255.0/24 Valid RIR databaseAPNIC 673 100% 66
2001:df1:a040::/48 Valid RIR databaseAPNIC 627 99% 67

AS-SET

AS133551 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 4 are in fix.csv.

  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: RIR103.54.148.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.54.149.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.54.150.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.54.151.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS133551 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.