bgpreport

Network · data from 2026-11-12

AS264206 Mixconect Telecom

Registry name: AS264206 - Mixconect Telecom Ltda Eireli, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264206, 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:242c::/34 No ROA Nonecovered by 2804:242c::/32 354 56% 64
2804:242c:4000::/34 No ROA Nonecovered by 2804:242c::/32 354 56% 64
2804:242c:8000::/34 No ROA Nonecovered by 2804:242c::/32 354 56% 64
138.97.180.0/24 No ROA Nonecovered by 138.97.180.0/23 10 1%low visibility 5
138.97.182.0/24 No ROA Nonecovered by 138.97.182.0/23 10 1%low visibility 5
138.97.183.0/24 No ROA Nonecovered by 138.97.182.0/23 2 0%low visibility 2
138.97.180.0/22 No ROA Other IRR onlyRADB, TC 667 99% 66
138.97.180.0/23 No ROA Other IRR onlyTC 666 99% 66
138.97.182.0/23 No ROA Other IRR onlyTC 666 99% 66
2804:242c::/32 No ROA Other IRR onlyRADB, TC 631 99% 67
138.97.181.0/24 No ROA Other IRR onlyRADB 10 1%low visibility 5

AS-SET

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

  • ROA: none11
  • Route object: none6
  • Route object: RIR5
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none2804:242c::/34No ROA covers it. Add a ROA for AS264206, maxLength 34.354 of 636
Route object: none2804:242c::/34No route object for it. A route object for 2804:242c::/32 with origin AS264206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264206 in the RIR database for the space.354 of 636
ROA: none2804:242c:4000::/34No ROA covers it. Add a ROA for AS264206, maxLength 34.354 of 636
Route object: none2804:242c:4000::/34No route object for it. A route object for 2804:242c::/32 with origin AS264206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264206 in the RIR database for the space.354 of 636
ROA: none2804:242c:8000::/34No ROA covers it. Add a ROA for AS264206, maxLength 34.354 of 636
Route object: none2804:242c:8000::/34No route object for it. A route object for 2804:242c::/32 with origin AS264206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264206 in the RIR database for the space.354 of 636
ROA: none138.97.180.0/24No ROA covers it. Add a ROA for AS264206, maxLength 24.10 of 673
Route object: none138.97.180.0/24No route object for it. A route object for 138.97.180.0/23 with origin AS264206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264206 in the RIR database for the space.10 of 673
ROA: none138.97.182.0/24No ROA covers it. Add a ROA for AS264206, maxLength 24.10 of 673
Route object: none138.97.182.0/24No route object for it. A route object for 138.97.182.0/23 with origin AS264206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264206 in the RIR database for the space.10 of 673
ROA: none138.97.183.0/24No ROA covers it. Add a ROA for AS264206, maxLength 24.2 of 673
Route object: none138.97.183.0/24No route object for it. A route object for 138.97.182.0/23 with origin AS264206 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264206 in the RIR database for the space.2 of 673
ROA: none138.97.180.0/22No ROA covers it. Add a ROA for AS264206, maxLength 22.667 of 673
Route object: RIR138.97.180.0/22Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
ROA: none138.97.180.0/23No ROA covers it. Add a ROA for AS264206, maxLength 23.666 of 673
Route object: RIR138.97.180.0/23Route object only in TC. Add it in the RIR database for the space.666 of 673
ROA: none138.97.182.0/23No ROA covers it. Add a ROA for AS264206, maxLength 23.666 of 673
Route object: RIR138.97.182.0/23Route object only in TC. Add it in the RIR database for the space.666 of 673
ROA: none2804:242c::/32No ROA covers it. Add a ROA for AS264206, maxLength 32.631 of 636
Route object: RIR2804:242c::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
ROA: none138.97.181.0/24No ROA covers it. Add a ROA for AS264206, maxLength 24.10 of 673
Route object: RIR138.97.181.0/24Route object only in RADB. Add it in the RIR database for the space.10 of 673
AS-SET: not foundAS-MIXCONECTPeeringDB names AS-MIXCONECT; no IRR database read has it.

Route objects not announced

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