bgpreport

Network · data from 2026-11-12

AS266002 Mundial Net

Registry name: AS266002 - MUNDIAL NET PROVEDOR DE INTERNET, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266002, 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:4114:c000::/36 No ROA Nonecovered by 2804:4114:c000::/34 3 0%low visibility 3
181.191.92.0/22 No ROA Other IRR onlyALTDB, RADB, TC 668 99% 67
181.191.92.0/23 No ROA Other IRR onlyALTDB, RADB 668 99% 67
181.191.94.0/23 No ROA Other IRR onlyALTDB, RADB 668 99% 67
2804:4114::/32 No ROA Other IRR onlyALTDB, RADB, TC 628 99% 67
2804:4114::/34 No ROA Other IRR onlyRADB 628 99% 67
2804:4114:c000::/34 No ROA Other IRR onlyALTDB 628 99% 67
2804:4114::/36 No ROA Other IRR onlyALTDB 328 52% 64

AS-SET

PeeringDB's irr_as_set for AS266002: AS266002:AS-MUNDIALNET. 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 (AS266002 isn't in the set, or no route object for AS266002 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 objectsAS266002 in itNot covered
AS266002:AS-MUNDIALNET ALTDB 1212 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 21 are in fix.csv.

  • ROA: none8
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none2804:4114:c000::/36No ROA covers it. Add a ROA for AS266002, maxLength 36.3 of 636
Route object: none2804:4114:c000::/36No route object for it. A route object for 2804:4114:c000::/34 with origin AS266002 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266002 in the RIR database for the space.3 of 636
ROA: none181.191.92.0/22No ROA covers it. Add a ROA for AS266002, maxLength 22.668 of 673
Route object: RIR181.191.92.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none181.191.92.0/23No ROA covers it. Add a ROA for AS266002, maxLength 23.668 of 673
Route object: RIR181.191.92.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
ROA: none181.191.94.0/23No ROA covers it. Add a ROA for AS266002, maxLength 23.668 of 673
Route object: RIR181.191.94.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
ROA: none2804:4114::/32No ROA covers it. Add a ROA for AS266002, maxLength 32.628 of 636
Route object: RIR2804:4114::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.628 of 636
ROA: none2804:4114::/34No ROA covers it. Add a ROA for AS266002, maxLength 34.628 of 636
Route object: RIR2804:4114::/34Route object only in RADB. Add it in the RIR database for the space.628 of 636
ROA: none2804:4114:c000::/34No ROA covers it. Add a ROA for AS266002, maxLength 34.628 of 636
Route object: RIR2804:4114:c000::/34Route object only in ALTDB. Add it in the RIR database for the space.628 of 636
ROA: none2804:4114::/36No ROA covers it. Add a ROA for AS266002, maxLength 36.328 of 636
Route object: RIR2804:4114::/36Route object only in ALTDB. Add it in the RIR database for the space.328 of 636

Route objects not announced

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

181.191.92.0/24ALTDB, RADB, TCNo ROA
181.191.93.0/24ALTDB, RADB, TCNo ROA
181.191.94.0/24ALTDB, RADB, TCNo ROA
181.191.95.0/24ALTDB, RADB, TCNo ROA
2804:4114::/48RADBNo ROA

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.