bgpreport

Network · data from 2026-11-12

AS262268 MAX NET TELECOMUNICAÇÕES

Registry name: AS262268 - MAX NET TELECOMUNICACOES, BR · PeeringDB

13IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
14No 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 AS262268, seen from no peer

Announced routes

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

177.23.88.0/21 No ROA Other IRR onlyRADB, TC 672 100% 66
177.23.88.0/24 No ROA Other IRR onlyRADB 670 100% 66
177.23.89.0/24 No ROA Other IRR onlyRADB 670 100% 66
177.23.90.0/23 No ROA Other IRR onlyRADB 670 100% 66
177.23.90.0/24 No ROA Other IRR onlyRADB 670 100% 66
177.23.91.0/24 No ROA Other IRR onlyRADB 670 100% 66
177.23.92.0/24 No ROA Other IRR onlyRADB 670 100% 66
177.23.93.0/24 No ROA Other IRR onlyRADB 670 100% 66
177.23.94.0/23 No ROA Other IRR onlyRADB 670 100% 66
177.23.94.0/24 No ROA Other IRR onlyRADB 670 100% 66
177.23.95.0/24 No ROA Other IRR onlyRADB 670 100% 66
177.23.88.0/23 No ROA Other IRR onlyRADB 669 99% 66
177.23.92.0/23 No ROA Other IRR onlyRADB 669 99% 66
2804:a4c::/32 No ROA Other IRR onlyRADB, TC 632 99% 67

AS-SET

PeeringDB's irr_as_set for AS262268: AS-262268. 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 (AS262268 isn't in the set, or no route object for AS262268 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 objectsAS262268 in itNot covered
AS-262268 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 29 are in fix.csv.

  • ROA: none14
  • Route object: RIR14
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none177.23.88.0/21No ROA covers it. Add a ROA for AS262268, maxLength 21.672 of 673
Route object: RIR177.23.88.0/21Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none177.23.88.0/24No ROA covers it. Add a ROA for AS262268, maxLength 24.670 of 673
Route object: RIR177.23.88.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.23.89.0/24No ROA covers it. Add a ROA for AS262268, maxLength 24.670 of 673
Route object: RIR177.23.89.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.23.90.0/23No ROA covers it. Add a ROA for AS262268, maxLength 23.670 of 673
Route object: RIR177.23.90.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.23.90.0/24No ROA covers it. Add a ROA for AS262268, maxLength 24.670 of 673
Route object: RIR177.23.90.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.23.91.0/24No ROA covers it. Add a ROA for AS262268, maxLength 24.670 of 673
Route object: RIR177.23.91.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.23.92.0/24No ROA covers it. Add a ROA for AS262268, maxLength 24.670 of 673
Route object: RIR177.23.92.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.23.93.0/24No ROA covers it. Add a ROA for AS262268, maxLength 24.670 of 673
Route object: RIR177.23.93.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.23.94.0/23No ROA covers it. Add a ROA for AS262268, maxLength 23.670 of 673
Route object: RIR177.23.94.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.23.94.0/24No ROA covers it. Add a ROA for AS262268, maxLength 24.670 of 673
Route object: RIR177.23.94.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.23.95.0/24No ROA covers it. Add a ROA for AS262268, maxLength 24.670 of 673
Route object: RIR177.23.95.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.23.88.0/23No ROA covers it. Add a ROA for AS262268, maxLength 23.669 of 673
Route object: RIR177.23.88.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none177.23.92.0/23No ROA covers it. Add a ROA for AS262268, maxLength 23.669 of 673
Route object: RIR177.23.92.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2804:a4c::/32No ROA covers it. Add a ROA for AS262268, maxLength 32.632 of 636
Route object: RIR2804:a4c::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636
AS-SET: not foundAS-262268PeeringDB names AS-262268; no IRR database read has it.

Route objects not announced

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