bgpreport

Network · data from 2026-11-12

AS199478 Radiokable

Registry name: RADIOCABLE-AS RADIOCABLE INGENIEROS S.L., ES · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS199478, 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.
37.130.144.0/24 Valid RIR databaseRIPE 673 100% 66
37.130.145.0/24 Valid RIR databaseRIPE 673 100% 66
37.130.146.0/24 Valid RIR databaseRIPE 673 100% 66
37.130.147.0/24 Valid RIR databaseRIPE 673 100% 66
37.130.148.0/24 Valid RIR databaseRIPE 673 100% 66
37.130.149.0/24 Valid RIR databaseRIPE 673 100% 66
37.130.150.0/24 Valid RIR databaseRIPE 673 100% 66
37.130.151.0/24 Valid RIR databaseRIPE 673 100% 66
91.193.152.0/24 Valid RIR databaseRIPE 673 100% 66
91.193.153.0/24 Valid RIR databaseRIPE 673 100% 66
91.193.154.0/24 Valid RIR databaseRIPE 673 100% 66
91.193.155.0/24 Valid RIR databaseRIPE 673 100% 66
144.2.164.0/24 Valid RIR databaseRIPE 673 100% 66
144.2.165.0/24 Valid RIR databaseRIPE 673 100% 66
144.2.166.0/24 Valid RIR databaseRIPE 673 100% 66
144.2.167.0/24 Valid RIR databaseRIPE 673 100% 66
185.16.208.0/24 Valid RIR databaseRIPE 673 100% 66
185.16.209.0/24 Valid RIR databaseRIPE 673 100% 66
185.16.210.0/24 Valid RIR databaseRIPE 673 100% 66
185.16.211.0/24 Valid RIR databaseRIPE 673 100% 66
185.157.152.0/24 Valid RIR databaseRIPE 673 100% 66
185.157.153.0/24 Valid RIR databaseRIPE 673 100% 66
185.157.154.0/24 Valid RIR databaseRIPE 673 100% 66
185.157.155.0/24 Valid RIR databaseRIPE 673 100% 66
185.251.104.0/24 Valid RIR databaseRIPE 673 100% 66
185.251.105.0/24 Valid RIR databaseRIPE 673 100% 66
185.251.106.0/24 Valid RIR databaseRIPE 673 100% 66
185.251.107.0/24 Valid RIR databaseRIPE 673 100% 66
193.84.19.0/24 Valid RIR databaseRIPE 673 100% 66
193.84.30.0/24 Valid RIR databaseRIPE 673 100% 66
193.84.70.0/24 Valid RIR databaseRIPE 673 100% 66
193.84.74.0/24 Valid RIR databaseRIPE 673 100% 66
194.62.158.0/24 Valid RIR databaseRIPE 673 100% 66
194.62.159.0/24 Valid RIR databaseRIPE 673 100% 66
194.62.190.0/24 Valid RIR databaseRIPE 673 100% 66
194.62.191.0/24 Valid RIR databaseRIPE 673 100% 66
213.170.248.0/24 Valid RIR databaseRIPE 673 100% 66
213.170.249.0/24 Valid RIR databaseRIPE 673 100% 66
213.170.250.0/24 Valid RIR databaseRIPE 673 100% 66
213.170.251.0/24 Valid RIR databaseRIPE 673 100% 66
213.170.252.0/24 Valid RIR databaseRIPE 673 100% 66
213.170.253.0/24 Valid RIR databaseRIPE 673 100% 66
213.170.254.0/24 Valid RIR databaseRIPE 673 100% 66
213.170.255.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

PeeringDB's irr_as_set for AS199478: RIPE::AS-RADIOKABLE. 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 (AS199478 isn't in the set, or no route object for AS199478 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 objectsAS199478 in itNot covered
RIPE::AS-RADIOKABLE RIPE 1144 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS199478 is announced.

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.