Network · data from 2026-11-12
AS271622 FOUR SOLUCOES E SERVICOS DE TELECOMUNICACOES LTDA
Registry name: AS271622 - FOUR SOLUCOES E SERVICOS DE TELECOMUNICACOES, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271622, 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.
| 45.163.48.0/22 | Valid | Other IRR onlyALTDB | 672 100% |
| 2804:7e68::/32 | Valid | Other IRR onlyALTDB, RADB | 634 100% |
| 45.163.48.0/24 | Valid | Other IRR onlyALTDB | 244 36% |
| 45.163.49.0/24 | Valid | Other IRR onlyALTDB | 244 36% |
| 45.163.50.0/24 | Valid | Other IRR onlyALTDB | 244 36% |
| 45.163.51.0/24 | Valid | Other IRR onlyALTDB | 244 36% |
AS-SET
PeeringDB's irr_as_set for AS271622: ALTDB::AS271622:AS-ALL. 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 (AS271622 isn't in the set, or no route object for AS271622 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 | AS271622 in it | Not covered |
|---|---|---|---|---|---|
| ALTDB::AS271622:AS-ALL | ALTDB | 1 | 3 | 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 10 are in fix.csv.
- Route object: RIR6
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 45.163.48.0/22 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:7e68::/32 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.163.48.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.163.49.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.163.50.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.163.51.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS271622 whose prefix no peer sees AS271622 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.163.48.0/23 | ALTDB | Valid |
| 45.163.50.0/23 | ALTDB | Valid |
| 2804:7e68::/33 | ALTDB | Invalid: maxLength |
| 2804:7e68:8000::/34 | ALTDB | Invalid: maxLength |
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.