Network · data from 2026-11-12
AS265237 AS265237 - SINAL TELECOM LTDA
Registry name: AS265237 - SINAL TELECOM LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265237, 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.
| 167.250.242.0/24 | Valid | Nonecovered by 167.250.242.0/23 | 672 100% |
| 167.250.243.0/24 | Valid | Nonecovered by 167.250.242.0/23 | 672 100% |
| 2804:2cb0:40::/42 | Valid | Nonecovered by 2804:2cb0::/32 | 634 100% |
| 2804:2cb0:80::/42 | Valid | Nonecovered by 2804:2cb0::/32 | 634 100% |
| 2804:2cb0:4000::/35 | Valid | Nonecovered by 2804:2cb0::/32 | 634 100% |
| 167.250.240.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 167.250.240.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 167.250.242.0/23 | Valid | Other IRR onlyRADB | 671 100% |
| 167.250.241.0/24 | Valid | Other IRR onlyRADB | 669 99% |
AS-SET
AS265237 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 11 are in fix.csv.
- Route object: none5
- Route object: RIR4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 167.250.242.0/24 | No route object for it. A route object for 167.250.242.0/23 with origin AS265237 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265237 in the RIR database for the space. |
| Route object: none | 167.250.243.0/24 | No route object for it. A route object for 167.250.242.0/23 with origin AS265237 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265237 in the RIR database for the space. |
| Route object: none | 2804:2cb0:40::/42 | No route object for it. A route object for 2804:2cb0::/32 with origin AS265237 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265237 in the RIR database for the space. |
| Route object: none | 2804:2cb0:80::/42 | No route object for it. A route object for 2804:2cb0::/32 with origin AS265237 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265237 in the RIR database for the space. |
| Route object: none | 2804:2cb0:4000::/35 | No route object for it. A route object for 2804:2cb0::/32 with origin AS265237 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265237 in the RIR database for the space. |
| Route object: RIR | 167.250.240.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 167.250.240.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 167.250.242.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 167.250.241.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265237 whose prefix no peer sees AS265237 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 167.250.240.0/22 | RADB, TC | No ROA |
| 2804:2cb0::/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.