Network · data from 2026-11-12
AS266532 MARGOTTO TELECOMUNICAÇÕES S/A
Registry name: AS266532 - MARGOTTO TELECOMUNICACOES S/A, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS266532, 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:3d74:101::/48 | Valid | Nonecovered by 2804:3d74::/32 | 296 47% |
| 187.62.192.0/24 | Valid | Other origin only | 213 32% |
| 2804:3d74:100::/48 | Valid | Other IRR onlyTC | 296 47% |
| 2804:3d74:102::/48 | Valid | Other IRR onlyTC | 296 47% |
AS-SET
AS266532's PeeringDB record names no 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 6 are in fix.csv.
- Route object: none2
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:3d74:101::/48 | No route object for it. A route object for 2804:3d74::/32 with origin AS266532 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266532 in the RIR database for the space. |
| Route object: none | 187.62.192.0/24 | Route objects for it name AS262617. Add a route object with origin AS266532 in the RIR database for the space. |
| Route object: RIR | 2804:3d74:100::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3d74:102::/48 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS266532 whose prefix no peer sees AS266532 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:2dec::/32 | RADB | No ROA |
| 2804:3d74::/32 | RADB, 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.