Network · data from 2026-11-12
AS270288 WISP SOLUCOES DE ACESSO
Registry name: AS270288 - WISP SOLUCOES DE ACESSO LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270288, 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.123.235.0/24 | No ROA | Nonecovered by 200.123.232.0/22 | 671 100% |
| 200.123.232.0/24 | Valid | Other IRR onlyTC | 669 99% |
| 200.123.233.0/24 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 200.123.234.0/24 | Valid | Other IRR onlyTC | 667 99% |
AS-SET
PeeringDB's irr_as_set for AS270288: TC::AS270288. 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 (AS270288 isn't in the set, or no route object for AS270288 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 | AS270288 in it | Not covered | |
|---|---|---|---|---|---|---|
| TC::AS270288 | A single AS number, not a set: AS270288 (this network), 6 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 8 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: RIR3
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 200.123.235.0/24 | No ROA covers it. Add a ROA for AS270288, maxLength 24. |
| Route object: none | 200.123.235.0/24 | No route object for it. A route object for 200.123.232.0/22 with origin AS270288 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270288 in the RIR database for the space. |
| Route object: RIR | 200.123.232.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.123.233.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.123.234.0/24 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS270288 whose prefix no peer sees AS270288 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.123.232.0/22 | RADB, TC | No ROA |
| 200.123.232.0/23 | TC | No ROA |
| 2804:69bc::/32 | RADB, TC | 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.