Network · data from 2026-11-12
AS263963 Goldweb Barretos serviços de Telecomunicações
Registry name: AS263963 - Goldweb Barretos servicos de Telecomunicacoes Ltda, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263963, 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.219.220.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 170.246.168.0/22 | Valid | Other IRR onlyNTTCOM, RADB, TC | 672 100% |
| 170.246.168.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 170.246.170.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 138.219.221.0/24 | Valid | Other IRR onlyRADB | 665 99% |
| 138.219.222.0/23 | Valid | Other IRR onlyRADB | 665 99% |
| 138.219.223.0/24 | Valid | Other IRR onlyRADB | 665 99% |
| 138.219.220.0/23 | Valid | Other IRR onlyRADB | 664 99% |
AS-SET
PeeringDB's irr_as_set for AS263963: AS263963. 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 (AS263963 isn't in the set, or no route object for AS263963 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 | AS263963 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS263963 | A single AS number, not a set: AS263963 (this network), 15 route objects. | |||||
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.
- Route object: RIR8
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 138.219.220.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.246.168.0/22 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.246.168.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.246.170.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.219.221.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.219.222.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.219.223.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.219.220.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263963 whose prefix no peer sees AS263963 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.219.220.0/24 | RADB | Valid |
| 138.219.222.0/24 | RADB | Valid |
| 170.246.168.0/24 | RADB | Valid |
| 170.246.169.0/24 | RADB | Valid |
| 170.246.170.0/24 | RADB | Valid |
| 170.246.171.0/24 | RADB | Valid |
| 2804:2878::/32 | NTTCOM, 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.