bgpreport

Network · data from 2026-11-12

AS138131 NATANETWORK SOLUTION

Registry name: IDNIC-NATANET-AS-ID - CV. NATANETWORK SOLUTION, ID · PeeringDB

12IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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 AS138131, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS138131, 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.121.122.0/24 Valid Other IRR onlyRADB 673 100% 69
103.133.56.0/24 Valid Other IRR onlyRADB 673 100% 69
103.164.172.0/24 Valid Other IRR onlyRADB 673 100% 69
103.180.165.0/24 Valid Other IRR onlyRADB 673 100% 69
103.180.164.0/23 Valid Other IRR onlyRADB 672 100% 67
103.180.164.0/24 Valid Other IRR onlyRADB 670 100% 69
103.142.21.0/24 Valid Other IRR onlyRADB 659 98% 69
103.115.164.0/24 Valid RIR databaseAPNIC 673 100% 69
103.164.173.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
157.15.77.0/24 Valid RIR databaseAPNIC 673 100% 69
160.187.143.0/24 Valid RIR databaseAPNIC 673 100% 69
160.236.68.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69

AS-SET

PeeringDB's irr_as_set for AS138131: AS-NATA. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS138131 isn't in the set, or no route object for AS138131 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS138131 in itNot covered
AS-NATA RADB 1112 Yes 0

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

  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
Route object: RIR103.121.122.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.133.56.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.164.172.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.180.165.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.180.164.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.180.164.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.142.21.0/24Route object only in RADB. Add it in the RIR database for the space.659 of 673

Route objects not announced

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