Network · data from 2026-11-12
AS271017 AMAZONFIBER SERVICOS DE COMUNICACAO
Registry name: AS271017 - AMAZONFIBER SERVICOS DE COMUNICACAO LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271017, 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.
| 200.219.2.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 200.219.0.0/23 | No ROA | Other IRR onlyRADB | 668 99% |
AS-SET
AS271017'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 15 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 200.219.2.0/23 | No ROA covers it. Add a ROA for AS271017, maxLength 23. |
| Route object: RIR | 200.219.2.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 200.219.0.0/23 | No ROA covers it. Add a ROA for AS271017, maxLength 23. |
| Route object: RIR | 200.219.0.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS271017 whose prefix no peer sees AS271017 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.219.0.0/22 | ALTDB | No ROA |
| 200.219.0.0/24 | RADB | No ROA |
| 200.219.1.0/24 | RADB | No ROA |
| 200.219.2.0/24 | RADB | No ROA |
| 200.219.3.0/24 | RADB | No ROA |
| 2804:7500::/32 | ALTDB | No ROA |
| 2804:7500::/44 | RADB | No ROA |
| 2804:7500:10::/44 | RADB | No ROA |
| 2804:7500:20::/44 | RADB | No ROA |
| 2804:7500:30::/44 | RADB | No ROA |
| 2804:7500:40::/44 | 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.