bgpreport

Network · data from 2026-11-12

AS269211 MUND NET TELECOMUNICAÇÕES LTDA ME

Registry name: AS269211 - MUND NET TELECOMUNICACOES LTDA ME, BR · PeeringDB

6IPv4 routes 0.0% RPKI valid · 66.7% with a route object
8IPv6 routes 0.0% RPKI valid · 25.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
14No ROA 8 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS269211, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269211, 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.
45.181.32.0/23 No ROA Nonecovered by 45.181.32.0/22 666 99% 67
2804:6114:8000::/35 No ROA Nonecovered by 2804:6114:8000::/34 331 52% 65
2804:6114:8000::/36 No ROA Nonecovered by 2804:6114:8000::/34 331 52% 65
2804:6114:9000::/36 No ROA Nonecovered by 2804:6114:8000::/34 331 52% 65
2804:6114:a000::/35 No ROA Nonecovered by 2804:6114:8000::/34 331 52% 65
2804:6114:a000::/36 No ROA Nonecovered by 2804:6114:8000::/34 331 52% 65
2804:6114:b000::/36 No ROA Nonecovered by 2804:6114:8000::/34 331 52% 65
45.181.34.0/24 No ROA Nonecovered by 45.181.34.0/23 63 9%low visibility 32
45.181.34.0/23 No ROA Other IRR onlyTC 671 100% 67
45.181.32.0/24 No ROA Other IRR onlyTC 666 99% 67
45.181.33.0/24 No ROA Other IRR onlyTC 666 99% 67
2804:6114:4000::/34 No ROA Other IRR onlyTC 630 99% 67
2804:6114:8000::/34 No ROA Other IRR onlyTC 332 52% 65
45.181.35.0/24 No ROA Other IRR onlyTC 64 10%low visibility 32

AS-SET

PeeringDB's irr_as_set for AS269211: AS269211:RS-ROUTES. 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 (AS269211 isn't in the set, or no route object for AS269211 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 objectsAS269211 in itNot covered
AS269211:RS-ROUTES A route-set, not an AS-SET; route-sets aren't expanded.

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

  • ROA: none14
  • Route object: none8
  • Route object: RIR6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none45.181.32.0/23No ROA covers it. Add a ROA for AS269211, maxLength 23.666 of 673
Route object: none45.181.32.0/23No route object for it. A route object for 45.181.32.0/22 with origin AS269211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269211 in the RIR database for the space.666 of 673
ROA: none2804:6114:8000::/35No ROA covers it. Add a ROA for AS269211, maxLength 35.331 of 636
Route object: none2804:6114:8000::/35No route object for it. A route object for 2804:6114:8000::/34 with origin AS269211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269211 in the RIR database for the space.331 of 636
ROA: none2804:6114:8000::/36No ROA covers it. Add a ROA for AS269211, maxLength 36.331 of 636
Route object: none2804:6114:8000::/36No route object for it. A route object for 2804:6114:8000::/34 with origin AS269211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269211 in the RIR database for the space.331 of 636
ROA: none2804:6114:9000::/36No ROA covers it. Add a ROA for AS269211, maxLength 36.331 of 636
Route object: none2804:6114:9000::/36No route object for it. A route object for 2804:6114:8000::/34 with origin AS269211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269211 in the RIR database for the space.331 of 636
ROA: none2804:6114:a000::/35No ROA covers it. Add a ROA for AS269211, maxLength 35.331 of 636
Route object: none2804:6114:a000::/35No route object for it. A route object for 2804:6114:8000::/34 with origin AS269211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269211 in the RIR database for the space.331 of 636
ROA: none2804:6114:a000::/36No ROA covers it. Add a ROA for AS269211, maxLength 36.331 of 636
Route object: none2804:6114:a000::/36No route object for it. A route object for 2804:6114:8000::/34 with origin AS269211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269211 in the RIR database for the space.331 of 636
ROA: none2804:6114:b000::/36No ROA covers it. Add a ROA for AS269211, maxLength 36.331 of 636
Route object: none2804:6114:b000::/36No route object for it. A route object for 2804:6114:8000::/34 with origin AS269211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269211 in the RIR database for the space.331 of 636
ROA: none45.181.34.0/24No ROA covers it. Add a ROA for AS269211, maxLength 24.63 of 673
Route object: none45.181.34.0/24No route object for it. A route object for 45.181.34.0/23 with origin AS269211 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269211 in the RIR database for the space.63 of 673
ROA: none45.181.34.0/23No ROA covers it. Add a ROA for AS269211, maxLength 23.671 of 673
Route object: RIR45.181.34.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none45.181.32.0/24No ROA covers it. Add a ROA for AS269211, maxLength 24.666 of 673
Route object: RIR45.181.32.0/24Route object only in TC. Add it in the RIR database for the space.666 of 673
ROA: none45.181.33.0/24No ROA covers it. Add a ROA for AS269211, maxLength 24.666 of 673
Route object: RIR45.181.33.0/24Route object only in TC. Add it in the RIR database for the space.666 of 673
ROA: none2804:6114:4000::/34No ROA covers it. Add a ROA for AS269211, maxLength 34.630 of 636
Route object: RIR2804:6114:4000::/34Route object only in TC. Add it in the RIR database for the space.630 of 636
ROA: none2804:6114:8000::/34No ROA covers it. Add a ROA for AS269211, maxLength 34.332 of 636
Route object: RIR2804:6114:8000::/34Route object only in TC. Add it in the RIR database for the space.332 of 636
ROA: none45.181.35.0/24No ROA covers it. Add a ROA for AS269211, maxLength 24.64 of 673
Route object: RIR45.181.35.0/24Route object only in TC. Add it in the RIR database for the space.64 of 673

Route objects not announced

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

45.181.32.0/22TCNo ROA
2804:6114::/32RADB, TCNo ROA
2804:6114::/34TCNo ROA
2804:6114:c000::/34TCNo 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.