Network · data from 2026-11-12
AS267498 VIDATEL SERVICOS CONVERGENTES EM TELECOMUNICACOES
Registry name: AS267498 - VIDATEL SERVICOS CONVERGENTES EM TELECOMUNICACOES, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267498, 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.
| 192.141.249.0/24 | Valid | Nonecovered by 192.141.248.0/23 | 670 100% |
| 2804:4268::/34 | Valid | Nonecovered by 2804:4268::/32 | 634 100% |
| 2804:4268:4000::/34 | Valid | Nonecovered by 2804:4268::/32 | 634 100% |
| 2804:4268:8000::/34 | Valid | Nonecovered by 2804:4268::/32 | 634 100% |
| 2804:4268:c000::/34 | Valid | Nonecovered by 2804:4268::/32 | 634 100% |
| 192.141.248.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 192.141.250.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 192.141.251.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 192.141.250.0/23 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 192.141.248.0/22 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 2804:4268::/32 | Valid | Other IRR onlyRADB | 2 0%low visibility |
AS-SET
AS267498'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 13 are in fix.csv.
- Route object: none5
- Route object: RIR6
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 192.141.249.0/24 | No route object for it. A route object for 192.141.248.0/23 with origin AS267498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267498 in the RIR database for the space. |
| Route object: none | 2804:4268::/34 | No route object for it. A route object for 2804:4268::/32 with origin AS267498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267498 in the RIR database for the space. |
| Route object: none | 2804:4268:4000::/34 | No route object for it. A route object for 2804:4268::/32 with origin AS267498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267498 in the RIR database for the space. |
| Route object: none | 2804:4268:8000::/34 | No route object for it. A route object for 2804:4268::/32 with origin AS267498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267498 in the RIR database for the space. |
| Route object: none | 2804:4268:c000::/34 | No route object for it. A route object for 2804:4268::/32 with origin AS267498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267498 in the RIR database for the space. |
| Route object: RIR | 192.141.248.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.141.250.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.141.251.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.141.250.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.141.248.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:4268::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267498 whose prefix no peer sees AS267498 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.228.228.0/22 | RADB | No ROA |
| 192.141.248.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.