Network · data from 2026-11-12
AS270306 PHOENIX TELECOMUNICACOES BR
Registry name: AS270306 - PHX TELECOM, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270306, 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.
| 190.112.164.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 190.112.164.0/23 | Valid | Other IRR onlyRADB, TC | 1 0%low visibility |
| 190.112.166.0/23 | Valid | Other IRR onlyTC | 1 0%low visibility |
AS-SET
AS270306'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 9 are in fix.csv.
- Route object: RIR3
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 190.112.164.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 190.112.164.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 190.112.166.0/23 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS270306 whose prefix no peer sees AS270306 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.112.164.0/24 | TC | Valid |
| 190.112.165.0/24 | TC | Valid |
| 190.112.166.0/24 | RADB, TC | Valid |
| 190.112.167.0/24 | RADB, TC | Valid |
| 2804:6a04::/32 | RADB, TC | Valid |
| 2804:6a04::/33 | RADB | 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.