Network · data from 2026-11-12
AS263562 AS263562 - Speet Servicos de Telecomunicacoes Ltda - ME
Registry name: AS263562 - Speet Servicos de Telecomunicacoes Ltda - ME, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263562, 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.
| 179.109.7.0/24 | Valid | Nonecovered by 179.109.6.0/23 | 667 99% |
| 179.109.0.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 179.109.2.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 179.109.3.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 179.109.4.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 179.109.5.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 179.109.1.0/24 | Valid | Other IRR onlyRADB | 666 99% |
| 179.109.6.0/24 | Valid | Other IRR onlyRADB | 666 99% |
| 2804:f00::/32 | Valid | Other IRR onlyRADB, TC | 632 99% |
AS-SET
AS263562 isn't in PeeringDB, where networks name their 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 16 are in fix.csv.
- Route object: none1
- Route object: RIR8
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 179.109.7.0/24 | No route object for it. A route object for 179.109.6.0/23 with origin AS263562 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263562 in the RIR database for the space. |
| Route object: RIR | 179.109.0.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 179.109.2.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 179.109.3.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 179.109.4.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 179.109.5.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 179.109.1.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 179.109.6.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:f00::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263562 whose prefix no peer sees AS263562 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 179.109.0.0/21 | RADB, TC | Valid |
| 179.109.0.0/22 | RADB | Valid |
| 179.109.0.0/23 | RADB | Valid |
| 179.109.2.0/23 | RADB | Valid |
| 179.109.4.0/22 | RADB | Valid |
| 179.109.4.0/23 | RADB | Valid |
| 179.109.6.0/23 | 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.