bgpreport

Network · data from 2026-11-12

AS206930 Tuyo_Internet Valor Information Technologies, S.L.

Registry name: Tuyo_Internet Valor Information Technologies, S.L., ES · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS206930, 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.
2a0a:e9c7::/32 Valid None 2 0%low visibility 2
185.216.130.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

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

  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2a0a:e9c7::/32No route object for it. Add a route object with origin AS206930 in the RIR database for the space.2 of 636

Route objects not announced

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

154.58.217.0/24RIPE-NONAUTHNo ROA
194.15.140.0/24RIPEValid

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.