bgpreport

Network · data from 2026-11-12

AS262196 Interface

Registry name: AS262196 - Interface, AR · PeeringDB

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

Announced routes

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

181.118.216.0/21 Valid Nonecovered by 181.118.208.0/20 1 0%low visibility 1
190.184.248.0/23 Valid Nonecovered by 190.184.248.0/22 1 0%low visibility 1
190.184.250.0/23 Valid Nonecovered by 190.184.248.0/22 1 0%low visibility 1
181.118.208.0/21 Valid Other IRR onlyRADB 1 0%low visibility 1
190.4.112.0/21 Valid Other IRR onlyRADB 1 0%low visibility 1
190.4.120.0/21 Valid Other IRR onlyRADB 1 0%low visibility 1
190.184.240.0/22 Valid Other IRR onlyRADB 1 0%low visibility 1
190.184.244.0/22 Valid Other IRR onlyRADB 1 0%low visibility 1
45.228.56.0/22 Valid RIR databaseLACNIC, RADB 671 100% 66
168.121.208.0/22 Valid RIR databaseLACNIC, RADB 671 100% 66
181.118.208.0/20 Valid RIR databaseLACNIC, RADB 671 100% 66
190.4.112.0/20 Valid RIR databaseLACNIC, RADB 670 100% 66
190.184.240.0/20 Valid RIR databaseLACNIC, RADB 670 100% 66
2800:ab0::/32 Valid RIR databaseLACNIC, RADB 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS262196: AS262196:AS-INTERFACENET. 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 (AS262196 isn't in the set, or no route object for AS262196 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 objectsAS262196 in itNot covered
AS262196:AS-INTERFACENET LACNIC 11198 No 14

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.

  • Route object: none3
  • Route object: RIR5
  • AS-SET: own ASN1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none181.118.216.0/21No route object for it. A route object for 181.118.208.0/20 with origin AS262196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262196 in the RIR database for the space.1 of 673
Route object: none190.184.248.0/23No route object for it. A route object for 190.184.248.0/22 with origin AS262196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262196 in the RIR database for the space.1 of 673
Route object: none190.184.250.0/23No route object for it. A route object for 190.184.248.0/22 with origin AS262196 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262196 in the RIR database for the space.1 of 673
Route object: RIR181.118.208.0/21Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: RIR190.4.112.0/21Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: RIR190.4.120.0/21Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: RIR190.184.240.0/22Route object only in RADB. Add it in the RIR database for the space.1 of 673
Route object: RIR190.184.244.0/22Route object only in RADB. Add it in the RIR database for the space.1 of 673
AS-SET: own ASNAS262196:AS-INTERFACENETAS262196 isn't in AS262196:AS-INTERFACENET (LACNIC) once expanded. Add AS262196 to it.

Route objects not announced

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

45.228.56.0/23RADBValid
45.228.58.0/24RADBValid
45.228.59.0/24RADBValid
181.118.216.0/22RADBValid
181.118.220.0/22RADBValid
190.184.248.0/22RADBValid
190.184.252.0/24RADBValid
190.184.254.0/24RADBValid

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.