Network · data from 2026-11-12
AS265144 MCD INFORMATICA E TELECOMUNICACOES
Registry name: AS265144 - MCD INFORMATICA E TELECOMUNICACOES LTDA - ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265144, 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:2b44:3400::/48 | Valid | Nonecovered by 2804:2b44::/32 | 636 100% |
| 2804:2b44:3732::/48 | Valid | Nonecovered by 2804:2b44::/32 | 636 100% |
| 2804:2b44::/33 | Valid | Nonecovered by 2804:2b44::/32 | 635 100% |
| 2804:2b44:3464::/48 | Valid | Nonecovered by 2804:2b44::/32 | 635 100% |
| 131.161.45.0/24 | Valid | Other IRR onlyTC | 673 100% |
| 143.255.109.0/24 | Valid | Other IRR onlyTC | 673 100% |
| 143.255.111.0/24 | Valid | Other IRR onlyTC | 673 100% |
| 131.161.44.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 131.161.46.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 143.255.108.0/22 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 143.255.108.0/24 | Valid | Other IRR onlyTC | 671 100% |
| 143.255.110.0/24 | Valid | Other IRR onlyTC | 671 100% |
| 131.161.47.0/24 | Valid | Other IRR onlyTC | 670 100% |
| 2804:2b44::/32 | Valid | Other IRR onlyRADB, TC | 635 100% |
| 2804:2b44:ff00::/40 | Valid | Other IRR onlyRADB | 635 100% |
| 2804:2b44:ff00::/41 | Valid | Other IRR onlyRADB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS265144: AS265144:AS-MCD. 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 (AS265144 isn't in the set, or no route object for AS265144 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 | AS265144 in it | Not covered |
|---|---|---|---|---|---|
| AS265144:AS-MCD | TC | 75 | 3 | 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 23 are in fix.csv.
- Route object: none4
- Route object: RIR12
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:2b44:3400::/48 | No route object for it. A route object for 2804:2b44::/32 with origin AS265144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265144 in the RIR database for the space. |
| Route object: none | 2804:2b44:3732::/48 | No route object for it. A route object for 2804:2b44::/32 with origin AS265144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265144 in the RIR database for the space. |
| Route object: none | 2804:2b44::/33 | No route object for it. A route object for 2804:2b44::/32 with origin AS265144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265144 in the RIR database for the space. |
| Route object: none | 2804:2b44:3464::/48 | No route object for it. A route object for 2804:2b44::/32 with origin AS265144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265144 in the RIR database for the space. |
| Route object: RIR | 131.161.45.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 143.255.109.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 143.255.111.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.161.44.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.161.46.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 143.255.108.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 143.255.108.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 143.255.110.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 131.161.47.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2b44::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2b44:ff00::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2b44:ff00::/41 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265144 whose prefix no peer sees AS265144 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.161.44.0/22 | RADB, TC | Valid |
| 131.161.44.0/23 | TC | Valid |
| 131.161.46.0/23 | TC | Valid |
| 143.255.108.0/23 | TC | Valid |
| 143.255.110.0/23 | TC | Valid |
| 201.77.147.0/24 | RADB | No ROA |
| 2804:2b44:8000::/40 | TC | Valid |
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.