Network · data from 2026-11-12
AS268836 SOW Telecomunicações
Registry name: AS268836 - sow telecomunicacoes ltda, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS268836, 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.
| 2804:5b58:4000::/34 | Valid | Nonecovered by 2804:5b58::/32 | 634 100% |
| 2804:5b58:8000::/34 | Valid | Nonecovered by 2804:5b58::/32 | 634 100% |
| 2804:5b58:c000::/34 | Valid | Nonecovered by 2804:5b58::/32 | 634 100% |
| 45.174.28.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 45.174.28.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 45.174.30.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 45.174.28.0/22 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 45.174.30.0/24 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 45.174.31.0/24 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 2804:5b58::/32 | Valid | Other IRR onlyRADB, TC | 635 100% |
| 2804:5b58::/34 | Valid | Other IRR onlyRADB | 635 100% |
AS-SET
AS268836's PeeringDB record names no 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 27 are in fix.csv.
- Route object: none3
- Route object: RIR8
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:5b58:4000::/34 | No route object for it. A route object for 2804:5b58::/32 with origin AS268836 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268836 in the RIR database for the space. |
| Route object: none | 2804:5b58:8000::/34 | No route object for it. A route object for 2804:5b58::/32 with origin AS268836 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268836 in the RIR database for the space. |
| Route object: none | 2804:5b58:c000::/34 | No route object for it. A route object for 2804:5b58::/32 with origin AS268836 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268836 in the RIR database for the space. |
| Route object: RIR | 45.174.28.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.174.28.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.174.30.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.174.28.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.174.30.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.174.31.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5b58::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5b58::/34 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS268836 whose prefix no peer sees AS268836 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.174.29.0/24 | TC | Valid |
| 2804:5b58:1000::/36 | TC | Valid |
| 2804:5b58:2000::/36 | TC | Valid |
| 2804:5b58:3000::/36 | TC | Valid |
| 2804:5b58:4000::/36 | TC | Valid |
| 2804:5b58:5000::/36 | TC | Valid |
| 2804:5b58:6000::/36 | TC | Valid |
| 2804:5b58:7000::/36 | TC | Valid |
| 2804:5b58:8000::/36 | TC | Valid |
| 2804:5b58:9000::/36 | TC | Valid |
| 2804:5b58:a000::/36 | TC | Valid |
| 2804:5b58:b000::/36 | TC | Valid |
| 2804:5b58:c000::/36 | TC | Valid |
| 2804:5b58:d000::/36 | TC | Valid |
| 2804:5b58:e000::/36 | RADB, TC | Valid |
| 2804:5b58:f000::/36 | 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.