Network · data from 2026-11-12
AS264267 AS264267 - TaboadoNET Com e M ltda me
Registry name: AS264267 - TaboadoNET Com e M ltda me, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264267, 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.
| 138.118.224.0/24 | Valid | Nonecovered by 138.118.224.0/22 | 2 0%low visibility |
| 138.118.225.0/24 | Valid | Nonecovered by 138.118.224.0/22 | 2 0%low visibility |
| 138.118.227.0/24 | Valid | Nonecovered by 138.118.224.0/22 | 2 0%low visibility |
| 2804:253c::/34 | Valid | Nonecovered by 2804:253c::/32 | 2 0%low visibility |
| 2804:253c:4000::/34 | Valid | Nonecovered by 2804:253c::/32 | 2 0%low visibility |
| 2804:253c:8000::/34 | Valid | Nonecovered by 2804:253c::/32 | 2 0%low visibility |
| 2804:253c:c000::/34 | Valid | Nonecovered by 2804:253c::/32 | 2 0%low visibility |
| 138.118.224.0/22 | Valid | Other IRR onlyTC | 671 100% |
| 2804:253c::/32 | Valid | Other IRR onlyTC | 633 100% |
AS-SET
AS264267 isn't in PeeringDB, where networks name their AS-SET.
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 9 are in fix.csv.
- Route object: none7
- Route object: RIR2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 138.118.224.0/24 | No route object for it. A route object for 138.118.224.0/22 with origin AS264267 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264267 in the RIR database for the space. |
| Route object: none | 138.118.225.0/24 | No route object for it. A route object for 138.118.224.0/22 with origin AS264267 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264267 in the RIR database for the space. |
| Route object: none | 138.118.227.0/24 | No route object for it. A route object for 138.118.224.0/22 with origin AS264267 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264267 in the RIR database for the space. |
| Route object: none | 2804:253c::/34 | No route object for it. A route object for 2804:253c::/32 with origin AS264267 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264267 in the RIR database for the space. |
| Route object: none | 2804:253c:4000::/34 | No route object for it. A route object for 2804:253c::/32 with origin AS264267 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264267 in the RIR database for the space. |
| Route object: none | 2804:253c:8000::/34 | No route object for it. A route object for 2804:253c::/32 with origin AS264267 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264267 in the RIR database for the space. |
| Route object: none | 2804:253c:c000::/34 | No route object for it. A route object for 2804:253c::/32 with origin AS264267 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264267 in the RIR database for the space. |
| Route object: RIR | 138.118.224.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:253c::/32 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS264267 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.