bgpreport

Network · data from 2026-11-12

AS262299 INEXA - Flavio Jose Penso Junior - ME

Registry name: AS262299 - FLAVIO JOSE PENSO JUNIOR LTDA, BR · PeeringDB

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

Announced routes

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

2804:a8c:c00::/42 Valid Nonecovered by 2804:a8c::/34 631 99% 68
200.108.160.0/22 Valid Other IRR onlyRADB, TC 671 100% 66
200.108.160.0/23 Valid Other IRR onlyRADB, TC 671 100% 66
177.54.240.0/23 Valid Other IRR onlyRADB, TC 669 99% 66
177.54.246.0/23 Valid Other IRR onlyRADB, TC 669 99% 66
177.54.248.0/21 Valid Other IRR onlyRADB, TC 669 99% 66
177.54.248.0/24 Valid Other IRR onlyRADB, TC 669 99% 66
177.54.250.0/23 Valid Other IRR onlyRADB, TC 669 99% 66
177.54.250.0/24 Valid Other IRR onlyRADB, TC 669 99% 66
177.54.252.0/23 Valid Other IRR onlyRADB, TC 669 99% 66
177.54.253.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
177.54.254.0/24 Valid Other IRR onlyRADB, TC 669 99% 66
177.54.255.0/24 Valid Other IRR onlyRADB, TC 669 99% 66
177.54.242.0/23 Valid Other IRR onlyRADB, TC 668 99% 66
177.54.244.0/23 Valid Other IRR onlyRADB, TC 668 99% 66
177.54.249.0/24 Valid Other IRR onlyRADB, TC 668 99% 66
177.54.251.0/24 Valid Other IRR onlyRADB, TC 668 99% 66
177.54.252.0/24 Valid Other IRR onlyRADB, TC 667 99% 67
200.108.160.0/24 Valid Other IRR onlyRADB, TC 667 99% 66
200.108.162.0/23 Valid Other IRR onlyRADB, TC 667 99% 67
200.108.162.0/24 Valid Other IRR onlyRADB, TC 667 99% 66
2804:a8c::/38 Valid Other IRR onlyRADB 632 99% 67
2804:a8c::/32 Valid Other IRR onlyRADB, TC 631 99% 67
2804:a8c::/34 Valid Other IRR onlyRADB, TC 356 56% 65
2804:a8c:4000::/34 Valid Other IRR onlyRADB, TC 356 56% 65
2804:a8c:8000::/34 Valid Other IRR onlyRADB, TC 356 56% 65
2804:a8c:c000::/34 Valid Other IRR onlyRADB, TC 356 56% 65
2804:a8c::/33 Valid Other IRR onlyRADB, TC 352 55% 65
2804:a8c:8000::/33 Valid Other IRR onlyRADB, TC 352 55% 65
177.54.241.0/24 Valid Other IRR onlyRADB, TC 212 32% 57
177.54.254.0/23 Valid Other IRR onlyRADB, TC 212 32% 57
177.54.248.0/23 Valid Other IRR onlyTC 202 30% 56
177.54.242.0/24 Valid Other IRR onlyRADB, TC 34 5%low visibility 13
177.54.244.0/24 Valid Other IRR onlyRADB, TC 34 5%low visibility 13
177.54.246.0/24 Valid Other IRR onlyRADB, TC 33 5%low visibility 12
200.108.161.0/24 Valid Other IRR onlyRADB, TC 33 5%low visibility 12
200.108.163.0/24 Valid Other IRR onlyRADB, TC 33 5%low visibility 12
177.54.243.0/24 Valid Other IRR onlyRADB, TC 31 5%low visibility 12
177.54.245.0/24 Valid Other IRR onlyRADB, TC 31 5%low visibility 12
177.54.240.0/24 Valid Other IRR onlyRADB, TC 30 4%low visibility 11

AS-SET

PeeringDB's irr_as_set for AS262299: AS-262299. 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 (AS262299 isn't in the set, or no route object for AS262299 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 objectsAS262299 in itNot covered
AS-262299 In no IRR database read today.

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

  • Route object: none1
  • Route object: RIR39
  • AS-SET: not found1
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
Route object: none2804:a8c:c00::/42No route object for it. A route object for 2804:a8c::/34 with origin AS262299 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262299 in the RIR database for the space.631 of 636
Route object: RIR200.108.160.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR200.108.160.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.54.240.0/23Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.54.246.0/23Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.54.248.0/21Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.54.248.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.54.250.0/23Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.54.250.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.54.252.0/23Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.54.253.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.54.254.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.54.255.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.54.242.0/23Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR177.54.244.0/23Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR177.54.249.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR177.54.251.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR177.54.252.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR200.108.160.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR200.108.162.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR200.108.162.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:a8c::/38Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:a8c::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:a8c::/34Route object only in RADB, TC. Add it in the RIR database for the space.356 of 636
Route object: RIR2804:a8c:4000::/34Route object only in RADB, TC. Add it in the RIR database for the space.356 of 636
Route object: RIR2804:a8c:8000::/34Route object only in RADB, TC. Add it in the RIR database for the space.356 of 636
Route object: RIR2804:a8c:c000::/34Route object only in RADB, TC. Add it in the RIR database for the space.356 of 636
Route object: RIR2804:a8c::/33Route object only in RADB, TC. Add it in the RIR database for the space.352 of 636
Route object: RIR2804:a8c:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.352 of 636
Route object: RIR177.54.241.0/24Route object only in RADB, TC. Add it in the RIR database for the space.212 of 673
Route object: RIR177.54.254.0/23Route object only in RADB, TC. Add it in the RIR database for the space.212 of 673
Route object: RIR177.54.248.0/23Route object only in TC. Add it in the RIR database for the space.202 of 673
Route object: RIR177.54.242.0/24Route object only in RADB, TC. Add it in the RIR database for the space.34 of 673
Route object: RIR177.54.244.0/24Route object only in RADB, TC. Add it in the RIR database for the space.34 of 673
Route object: RIR177.54.246.0/24Route object only in RADB, TC. Add it in the RIR database for the space.33 of 673
Route object: RIR200.108.161.0/24Route object only in RADB, TC. Add it in the RIR database for the space.33 of 673
Route object: RIR200.108.163.0/24Route object only in RADB, TC. Add it in the RIR database for the space.33 of 673
Route object: RIR177.54.243.0/24Route object only in RADB, TC. Add it in the RIR database for the space.31 of 673
Route object: RIR177.54.245.0/24Route object only in RADB, TC. Add it in the RIR database for the space.31 of 673
Route object: RIR177.54.240.0/24Route object only in RADB, TC. Add it in the RIR database for the space.30 of 673
AS-SET: not foundAS-262299PeeringDB names AS-262299; no IRR database read has it.

Route objects not announced

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

45.236.63.0/24RADBNo ROA
167.249.70.0/23RADBNo ROA
177.54.240.0/20RADB, TCValid
177.54.240.0/21RADB, TCValid
177.54.240.0/22RADB, TCValid
177.54.244.0/22RADB, TCValid
177.54.247.0/24RADB, TCValid
177.54.248.0/22TCValid
177.54.252.0/22TCValid
2804:a8c:200::/39RADBValid

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.