bgpreport

Network · data from 2026-11-12

AS52300 Internet Local

Registry name: AS52300 - Internet Local, AR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52300, 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.

2803:2ac0:5000::/36 Valid Nonecovered by 2803:2ac0::/32 21 3%low visibility 14
2803:2ac0:8000::/36 Valid Nonecovered by 2803:2ac0::/32 21 3%low visibility 14
190.110.180.0/22 Valid Nonecovered by 190.110.176.0/21 10 1%low visibility 8
190.110.176.0/22 Valid Nonecovered by 190.110.176.0/21 2 0%low visibility 2
190.110.176.0/23 Valid Nonecovered by 190.110.176.0/21 2 0%low visibility 2
190.110.178.0/23 Valid Nonecovered by 190.110.176.0/21 2 0%low visibility 2
190.110.180.0/23 Valid Nonecovered by 190.110.176.0/21 2 0%low visibility 2
190.110.182.0/23 Valid Nonecovered by 190.110.176.0/21 2 0%low visibility 2
190.110.180.0/24 Valid Other IRR onlyRADB 670 100% 66
190.110.183.0/24 Valid Other IRR onlyRADB 670 100% 66
190.110.176.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
190.110.177.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
190.110.178.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
190.110.179.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
190.110.181.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
190.110.182.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
190.110.176.0/21 Valid RIR databaseLACNIC, RADB 670 100% 67
2803:2ac0::/32 Valid RIR databaseLACNIC, RADB 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS52300: AS52300:AS-ALL. 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 (AS52300 isn't in the set, or no route object for AS52300 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 objectsAS52300 in itNot covered
AS52300:AS-ALL LACNIC 16511,826 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 16 are in fix.csv.

  • Route object: none8
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
Route object: none2803:2ac0:5000::/36No route object for it. A route object for 2803:2ac0::/32 with origin AS52300 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52300 in the RIR database for the space.21 of 636
Route object: none2803:2ac0:8000::/36No route object for it. A route object for 2803:2ac0::/32 with origin AS52300 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52300 in the RIR database for the space.21 of 636
Route object: none190.110.180.0/22No route object for it. A route object for 190.110.176.0/21 with origin AS52300 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52300 in the RIR database for the space.10 of 673
Route object: none190.110.176.0/22No route object for it. A route object for 190.110.176.0/21 with origin AS52300 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52300 in the RIR database for the space.2 of 673
Route object: none190.110.176.0/23No route object for it. A route object for 190.110.176.0/21 with origin AS52300 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52300 in the RIR database for the space.2 of 673
Route object: none190.110.178.0/23No route object for it. A route object for 190.110.176.0/21 with origin AS52300 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52300 in the RIR database for the space.2 of 673
Route object: none190.110.180.0/23No route object for it. A route object for 190.110.176.0/21 with origin AS52300 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52300 in the RIR database for the space.2 of 673
Route object: none190.110.182.0/23No route object for it. A route object for 190.110.176.0/21 with origin AS52300 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52300 in the RIR database for the space.2 of 673
Route object: RIR190.110.180.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.110.183.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR190.110.176.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR190.110.177.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR190.110.178.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR190.110.179.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR190.110.181.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR190.110.182.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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