Network · data from 2026-11-12
AS262988 Pombonet Telecomunicações
Registry name: AS262988 - Pombonet Telecomunicacoes e Informatica, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS262988, 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.
| 168.90.80.0/22 | Valid | Other IRR onlyTC | 670 100% |
| 179.125.64.0/19 | Valid | Other IRR onlyTC | 670 100% |
| 186.251.8.0/22 | Valid | Other IRR onlyTC | 670 100% |
| 2804:1058::/32 | Valid | Other IRR onlyTC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS262988: AS262988:AS-POMBONET. 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 (AS262988 isn't in the set, or no route object for AS262988 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 | AS262988 in it | Not covered |
|---|---|---|---|---|---|
| AS262988:AS-POMBONET | TC | 14 | 1 | 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 55 are in fix.csv.
- Route object: RIR4
- Route object: not announced51
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 168.90.80.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 179.125.64.0/19 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 186.251.8.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1058::/32 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS262988 whose prefix no peer sees AS262988 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 168.90.80.0/23 | TC | Valid |
| 168.90.80.0/24 | TC | Valid |
| 168.90.81.0/24 | TC | Valid |
| 168.90.82.0/23 | TC | Valid |
| 168.90.82.0/24 | TC | Valid |
| 168.90.83.0/24 | TC | Valid |
| 179.125.64.0/20 | TC | Valid |
| 179.125.64.0/22 | TC | Valid |
| 179.125.64.0/23 | TC | Valid |
| 179.125.64.0/24 | TC | Valid |
| 179.125.65.0/24 | TC | Valid |
| 179.125.66.0/23 | TC | Valid |
| 179.125.66.0/24 | TC | Valid |
| 179.125.67.0/24 | TC | Valid |
| 179.125.68.0/24 | TC | Valid |
| 179.125.69.0/24 | TC | Valid |
| 179.125.70.0/24 | TC | Valid |
| 179.125.71.0/24 | TC | Valid |
| 179.125.72.0/24 | TC | Valid |
| 179.125.73.0/24 | TC | Valid |
| 179.125.74.0/24 | TC | Valid |
| 179.125.75.0/24 | TC | Valid |
| 179.125.76.0/24 | TC | Valid |
| 179.125.77.0/24 | TC | Valid |
| 179.125.78.0/24 | TC | Valid |
| 179.125.79.0/24 | TC | Valid |
| 179.125.80.0/24 | TC | Valid |
| 179.125.81.0/24 | TC | Valid |
| 179.125.82.0/24 | TC | Valid |
| 179.125.83.0/24 | TC | Valid |
| 179.125.84.0/24 | TC | Valid |
| 179.125.85.0/24 | TC | Valid |
| 179.125.86.0/24 | TC | Valid |
| 179.125.87.0/24 | TC | Valid |
| 179.125.88.0/24 | TC | Valid |
| 179.125.89.0/24 | TC | Valid |
| 179.125.90.0/24 | TC | Valid |
| 179.125.91.0/24 | TC | Valid |
| 179.125.92.0/22 | TC | Valid |
| 179.125.92.0/24 | TC | Valid |
| 179.125.93.0/24 | TC | Valid |
| 179.125.94.0/24 | TC | Valid |
| 179.125.95.0/24 | TC | Valid |
| 186.251.8.0/23 | TC | Valid |
| 186.251.8.0/24 | TC | Valid |
| 186.251.9.0/24 | TC | Valid |
| 186.251.10.0/23 | TC | Valid |
| 186.251.10.0/24 | TC | Valid |
| 186.251.11.0/24 | TC | Valid |
| 2804:1058::/33 | TC | Valid |
| 2804:1058::/34 | 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.