Network · data from 2026-11-12
AS266101 E M C TAVARES SERVIÇOS DE INFORMÁTICA
Registry name: AS266101 - MARTINS.NET SERVICOS DE TELECOMUNICACOES LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS266101, 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.
| 45.5.212.0/22 | No ROA | Other IRR onlyALTDB, RADB, TC | 664 99% |
| 45.5.212.0/23 | No ROA | Other IRR onlyRADB, TC | 664 99% |
| 45.5.214.0/23 | No ROA | Other IRR onlyRADB, TC | 664 99% |
| 45.5.213.0/24 | No ROA | Other IRR onlyRADB, TC | 653 97% |
| 45.5.215.0/24 | No ROA | Other IRR onlyRADB, TC | 653 97% |
| 45.5.212.0/24 | No ROA | Other IRR onlyRADB, TC | 652 97% |
| 45.5.214.0/24 | No ROA | Other IRR onlyRADB, TC | 652 97% |
| 2804:3aa4::/32 | No ROA | Other IRR onlyALTDB, RADB, TC | 625 98% |
AS-SET
PeeringDB's irr_as_set for AS266101: AS266101:AS-ANNOUNCEMENTS. 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 (AS266101 isn't in the set, or no route object for AS266101 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 | AS266101 in it | Not covered |
|---|---|---|---|---|---|
| AS266101:AS-ANNOUNCEMENTS | TC | 5 | 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 19 are in fix.csv.
- ROA: none8
- Route object: RIR8
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.5.212.0/22 | No ROA covers it. Add a ROA for AS266101, maxLength 22. |
| Route object: RIR | 45.5.212.0/22 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 45.5.212.0/23 | No ROA covers it. Add a ROA for AS266101, maxLength 23. |
| Route object: RIR | 45.5.212.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 45.5.214.0/23 | No ROA covers it. Add a ROA for AS266101, maxLength 23. |
| Route object: RIR | 45.5.214.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 45.5.213.0/24 | No ROA covers it. Add a ROA for AS266101, maxLength 24. |
| Route object: RIR | 45.5.213.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 45.5.215.0/24 | No ROA covers it. Add a ROA for AS266101, maxLength 24. |
| Route object: RIR | 45.5.215.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 45.5.212.0/24 | No ROA covers it. Add a ROA for AS266101, maxLength 24. |
| Route object: RIR | 45.5.212.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 45.5.214.0/24 | No ROA covers it. Add a ROA for AS266101, maxLength 24. |
| Route object: RIR | 45.5.214.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:3aa4::/32 | No ROA covers it. Add a ROA for AS266101, maxLength 32. |
| Route object: RIR | 2804:3aa4::/32 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS266101 whose prefix no peer sees AS266101 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:3aa4::/33 | TC | No ROA |
| 2804:3aa4:c0::/46 | RADB | No ROA |
| 2804:3aa4:8000::/33 | TC | 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.