bgpreport

Network · data from 2026-11-12

AS199685 FIRST-SERVER-EU-WEST FIRST SERVER, SOCIEDAD LIMITADA

Registry name: FIRST-SERVER-EU-WEST FIRST SERVER, SOCIEDAD LIMITADA, ES · not in PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
52Route objects not announced registered with origin AS199685, seen from no peer

Announced routes

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

46.8.122.0/23 Valid RIR databaseRIPE 673 100% 67
83.147.242.0/23 Valid RIR databaseRIPE 673 100% 67
109.248.24.0/23 Valid RIR databaseRIPE 673 100% 67
135.136.184.0/23 Valid RIR databaseRIPE 673 100% 67
2a0c:5d00:3006::/48 Valid RIR databaseRIPE 636 100% 67
2a0c:5d00:3003::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

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

  • Route object: not announced52

Route objects not announced

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

46.8.122.0/24RIPEValid
46.8.123.0/24RIPEValid
80.76.34.0/23RIPEValid
80.76.34.0/24RIPEValid
80.76.35.0/24RIPEValid
83.147.242.0/24RIPEValid
83.147.243.0/24RIPEValid
89.44.84.0/23RIPEValid
89.44.84.0/24RIPEValid
89.44.85.0/24RIPEValid
91.103.252.0/23RIPEValid
91.103.252.0/24RIPEValid
91.103.253.0/24RIPEValid
91.186.214.0/23RIPEValid
91.186.214.0/24RIPEValid
91.186.215.0/24RIPEValid
94.142.136.0/23RIPEValid
94.142.136.0/24RIPEValid
94.142.137.0/24RIPEValid
103.249.132.0/23RIPEValid
103.249.132.0/24RIPEValid
103.249.133.0/24RIPEValid
109.69.56.0/23RIPEValid
109.69.56.0/24RIPEValid
109.69.57.0/24RIPEValid
109.248.24.0/24RIPEValid
109.248.25.0/24RIPEValid
135.136.184.0/24RIPEValid
135.136.185.0/24RIPEValid
159.255.34.0/24RIPEValid
159.255.35.0/24RIPEValid
185.94.164.0/23RIPEValid
185.94.164.0/24RIPEValid
185.94.165.0/24RIPEValid
185.103.254.0/23RIPEValid
185.103.254.0/24RIPEValid
185.103.255.0/24RIPEValid
185.114.72.0/23RIPEValid
185.114.72.0/24RIPEValid
185.114.73.0/24RIPEValid
185.174.136.0/23RIPEValid
185.174.136.0/24RIPEValid
185.174.137.0/24RIPEValid
185.233.202.0/23RIPEValid
185.233.202.0/24RIPEValid
185.233.203.0/24RIPEValid
193.124.188.0/23RIPEValid
193.124.188.0/24RIPEValid
193.124.189.0/24RIPEValid
2a04:5201:7::/48RIPEValid
2a04:5201:9::/48RIPEValid
2a0c:f644:ffff::/48RIPENo 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.