bgpreport

Network · data from 2026-11-12

AS268101 MIO TELECOM LTDA

Registry name: AS268101 - MIO TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268101, 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:5808::/34 Valid Nonecovered by 2804:5808::/32 629 99% 67
2804:5808:4000::/34 Valid Nonecovered by 2804:5808::/32 629 99% 67
2804:5808:8000::/34 Valid Nonecovered by 2804:5808::/32 629 99% 67
2804:5808:c000::/34 Valid Nonecovered by 2804:5808::/32 629 99% 67
45.168.156.0/22 Valid Other IRR onlyRADB, TC 668 99% 66
45.168.156.0/23 Valid Other IRR onlyRADB, TC 668 99% 66
45.168.158.0/23 Valid Other IRR onlyRADB, TC 668 99% 66
45.168.158.0/24 Valid Other IRR onlyRADB, TC 668 99% 66
45.168.156.0/24 Valid Other IRR onlyRADB, TC 667 99% 66
45.168.157.0/24 Valid Other IRR onlyRADB, TC 667 99% 66
45.168.159.0/24 Valid Other IRR onlyRADB, TC 667 99% 66
2804:5808::/32 Valid Other IRR onlyRADB, TC 629 99% 67

AS-SET

PeeringDB's irr_as_set for AS268101: AS268101:AS-MIO-ALL. 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 (AS268101 isn't in the set, or no route object for AS268101 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 objectsAS268101 in itNot covered
AS268101:AS-MIO-ALL TC1 member set in no database: AS268101:AS-MIO-CUSTOM 128 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 13 are in fix.csv.

  • Route object: none4
  • Route object: RIR8
  • AS-SET: missing member1
ChangePrefix or setDetailFull-table peers
Route object: none2804:5808::/34No route object for it. A route object for 2804:5808::/32 with origin AS268101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268101 in the RIR database for the space.629 of 636
Route object: none2804:5808:4000::/34No route object for it. A route object for 2804:5808::/32 with origin AS268101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268101 in the RIR database for the space.629 of 636
Route object: none2804:5808:8000::/34No route object for it. A route object for 2804:5808::/32 with origin AS268101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268101 in the RIR database for the space.629 of 636
Route object: none2804:5808:c000::/34No route object for it. A route object for 2804:5808::/32 with origin AS268101 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268101 in the RIR database for the space.629 of 636
Route object: RIR45.168.156.0/22Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR45.168.156.0/23Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR45.168.158.0/23Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR45.168.158.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR45.168.156.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR45.168.157.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR45.168.159.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:5808::/32Route object only in RADB, TC. Add it in the RIR database for the space.629 of 636
AS-SET: missing memberAS268101:AS-MIO-ALLAS268101:AS-MIO-ALL (TC) lists AS268101:AS-MIO-CUSTOM; no IRR database read has it.

Route objects not announced

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