bgpreport

Network · data from 2026-11-12

AS272535 VIXNET TELECOM SERVICOS DE COMUNICACAO

Registry name: AS272535 - VIXNET TELECOM SERVICOS DE COMUNICACAO LTDA, BR · PeeringDB

4IPv4 routes 100.0% RPKI valid · 25.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 3 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
12Route objects not announced registered with origin AS272535, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS272535, 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.

201.94.152.14/32 Valid Nonecovered by 201.94.152.0/24 1 0%low visibility 2
201.94.152.17/32 Valid Nonecovered by 201.94.152.0/24 1 0%low visibility 2
201.94.152.18/32 Valid Nonecovered by 201.94.152.0/24 1 0%low visibility 2
201.94.152.0/22 Valid Other IRR onlyRADB, TC 668 99% 67
2804:82b4::/32 Valid Other IRR onlyRADB, TC 633 100% 67

AS-SET

AS272535'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 17 are in fix.csv.

  • Route object: none3
  • Route object: RIR2
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
Route object: none201.94.152.14/32No route object for it. A route object for 201.94.152.0/24 with origin AS272535 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS272535 in the RIR database for the space.1 of 673
Route object: none201.94.152.17/32No route object for it. A route object for 201.94.152.0/24 with origin AS272535 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS272535 in the RIR database for the space.1 of 673
Route object: none201.94.152.18/32No route object for it. A route object for 201.94.152.0/24 with origin AS272535 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS272535 in the RIR database for the space.1 of 673
Route object: RIR201.94.152.0/22Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:82b4::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

Route objects with origin AS272535 whose prefix no peer sees AS272535 announce. Many are kept on purpose (backup routes, space announced only in some places).

201.94.152.0/23TCValid
201.94.152.0/24TCValid
201.94.153.0/24TCValid
201.94.154.0/23TCValid
201.94.154.0/24TCValid
201.94.155.0/24TCValid
2804:82b4::/33TCValid
2804:82b4::/34RADB, TCValid
2804:82b4:4000::/34RADB, TCValid
2804:82b4:8000::/33TCValid
2804:82b4:8000::/34RADB, TCValid
2804:82b4:c000::/34RADB, TCValid

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.