Network · data from 2026-11-12
AS264386 MMM E G TELECOMUNICACOES LTDA - ME
Registry name: AS264386 - MMM E G TELECOMUNICACOES LTDA - ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264386, 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.
| 131.108.172.0/23 | Invalid: maxLength | Nonecovered by 131.108.172.0/22 | 1 0%low visibility |
| 131.108.174.0/23 | Invalid: maxLength | Nonecovered by 131.108.172.0/22 | 1 0%low visibility |
| 177.38.88.0/22 | Valid | Other IRR onlyTC | 669 99% |
| 177.38.88.0/23 | Valid | Other IRR onlyTC | 669 99% |
| 177.38.88.0/24 | Valid | Other IRR onlyTC | 669 99% |
| 177.38.89.0/24 | Valid | Other IRR onlyTC | 669 99% |
| 177.38.90.0/23 | Valid | Other IRR onlyTC | 669 99% |
| 177.38.90.0/24 | Valid | Other IRR onlyTC | 669 99% |
| 177.38.91.0/24 | Valid | Other IRR onlyTC | 669 99% |
| 131.108.172.0/22 | Valid | Other IRR onlyALTDB, RADB, TC | 668 99% |
| 168.197.80.0/22 | Valid | Other IRR onlyALTDB, RADB, TC | 668 99% |
| 45.6.240.0/24 | Valid | Other IRR onlyTC | 666 99% |
| 2804:1db0::/32 | Valid | Other IRR onlyALTDB, RADB, TC | 635 100% |
| 2804:1db0::/33 | Valid | Other IRR onlyTC | 349 55% |
| 2804:1db0:8000::/33 | Valid | Other IRR onlyTC | 349 55% |
| 168.197.80.0/23 | Valid | Other IRR onlyTC | 206 31% |
| 168.197.82.0/23 | Valid | Other IRR onlyTC | 206 31% |
| 168.197.82.0/24 | Valid | Other IRR onlyRADB, TC | 205 30% |
AS-SET
PeeringDB's irr_as_set for AS264386: AS264386:AS-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 (AS264386 isn't in the set, or no route object for AS264386 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.
| Name | Database | ASNs | Sets | AS264386 in it | Not covered |
|---|---|---|---|---|---|
| AS264386:AS-ALL | TC | 16 | 2 | 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 27 are in fix.csv.
- ROA: maxLength2
- Route object: none2
- Route object: RIR16
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 131.108.172.0/23 | ROA 131.108.172.0/22 AS264386 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 131.108.172.0/23. |
| Route object: none | 131.108.172.0/23 | No route object for it. A route object for 131.108.172.0/22 with origin AS264386 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264386 in the RIR database for the space. |
| ROA: maxLength | 131.108.174.0/23 | ROA 131.108.172.0/22 AS264386 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 131.108.174.0/23. |
| Route object: none | 131.108.174.0/23 | No route object for it. A route object for 131.108.172.0/22 with origin AS264386 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264386 in the RIR database for the space. |
| Route object: RIR | 177.38.88.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.88.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.88.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.89.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.90.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.90.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.91.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.108.172.0/22 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.197.80.0/22 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.6.240.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1db0::/32 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1db0::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1db0:8000::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.197.80.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.197.82.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.197.82.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS264386 whose prefix no peer sees AS264386 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.6.240.0/22 | RADB | No ROA |
| 45.6.240.0/23 | TC | Valid |
| 45.6.241.0/24 | TC | Valid |
| 168.197.80.0/24 | TC | Valid |
| 168.197.81.0/24 | TC | Valid |
| 168.197.83.0/24 | TC | Valid |
| 177.38.88.0/21 | RADB | No 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.