bgpreport

Network · data from 2026-11-12

AS273658 VIRTUAX PROVIMENTO SERVICOS DE TELECOMUNICACOES LT

Registry name: AS273658 - VIRTUAX PROVIMENTO SERVICOS DE TELECOMUNICACOES LT, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273658, 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:8a44::/33 No ROA Nonecovered by 2804:8a44::/32 634 100% 67
2804:8a44:8000::/33 No ROA Nonecovered by 2804:8a44::/32 634 100% 67
2804:8a44::/32 No ROA Other IRR onlyALTDB, RADB 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS273658: AS-273658. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS273658 isn't in the set, or no route object for AS273658 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS273658 in itNot covered
AS-273658 ALTDB 91120 Yes 0

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

  • ROA: none3
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2804:8a44::/33No ROA covers it. Add a ROA for AS273658, maxLength 33.634 of 636
Route object: none2804:8a44::/33No route object for it. A route object for 2804:8a44::/32 with origin AS273658 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273658 in the RIR database for the space.634 of 636
ROA: none2804:8a44:8000::/33No ROA covers it. Add a ROA for AS273658, maxLength 33.634 of 636
Route object: none2804:8a44:8000::/33No route object for it. A route object for 2804:8a44::/32 with origin AS273658 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273658 in the RIR database for the space.634 of 636
ROA: none2804:8a44::/32No ROA covers it. Add a ROA for AS273658, maxLength 32.633 of 636
Route object: RIR2804:8a44::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

2804:1ef4::/32RADBNo 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.