Network · data from 2026-11-12
AS267020 VS TELECOM
Registry name: AS267020 - VS COMUNICACAO E MULTIMIDIA LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267020, 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:46ec:800::/40 | Valid | Nonecovered by 2804:46ec::/32 | 634 100% |
| 2804:46ec:4000::/40 | Valid | Nonecovered by 2804:46ec::/32 | 631 99% |
| 2804:46ec:aa00::/40 | Valid | Nonecovered by 2804:46ec::/32 | 631 99% |
| 45.226.98.0/23 | Valid | Other IRR onlyALTDB, TC | 671 100% |
| 45.226.96.0/23 | Valid | Other IRR onlyTC | 667 99% |
| 2804:46ec:700::/40 | Valid | Other IRR onlyTC | 634 100% |
| 2804:46ec:2200::/40 | Valid | Other IRR onlyTC | 631 99% |
| 2804:46ec:3300::/40 | Valid | Other IRR onlyTC | 631 99% |
| 45.226.96.0/24 | Valid | Other IRR onlyALTDB, TC | 39 6%low visibility |
| 45.226.97.0/24 | Valid | Other IRR onlyALTDB, TC | 39 6%low visibility |
AS-SET
AS267020'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 14 are in fix.csv.
- Route object: none3
- Route object: RIR7
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:46ec:800::/40 | No route object for it. A route object for 2804:46ec::/32 with origin AS267020 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267020 in the RIR database for the space. |
| Route object: none | 2804:46ec:4000::/40 | No route object for it. A route object for 2804:46ec::/32 with origin AS267020 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267020 in the RIR database for the space. |
| Route object: none | 2804:46ec:aa00::/40 | No route object for it. A route object for 2804:46ec::/32 with origin AS267020 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267020 in the RIR database for the space. |
| Route object: RIR | 45.226.98.0/23 | Route object only in ALTDB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.226.96.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:46ec:700::/40 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:46ec:2200::/40 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:46ec:3300::/40 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.226.96.0/24 | Route object only in ALTDB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.226.97.0/24 | Route object only in ALTDB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267020 whose prefix no peer sees AS267020 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.226.96.0/22 | RADB, TC | Valid |
| 45.226.98.0/24 | ALTDB, TC | Valid |
| 45.226.99.0/24 | ALTDB, TC | Valid |
| 2804:46ec::/32 | 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.