bgpreport

Network · data from 2026-11-12

AS8903 LYNTIA NETWORKS (Main AS)

Registry name: AS8903 LYNTIA NETWORKS S.A., ES · PeeringDB

111IPv4 routes 91.9% RPKI valid · 86.5% with a route object
8IPv6 routes 100.0% RPKI valid · 75.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
9No ROA 17 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
71Route objects not announced registered with origin AS8903, seen from no peer

Announced routes

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

149.7.217.0/24 No ROA Other origin only 646 96% 67
154.58.219.0/24 No ROA Other origin only 641 95% 67
154.62.64.0/24 No ROA None 641 95% 67
154.62.65.0/24 No ROA None 641 95% 67
154.62.234.0/23 No ROA Other origin only 641 95% 67
154.62.67.0/24 No ROA None 639 95% 67
154.62.251.0/24 No ROA Other origin only 639 95% 67
154.44.190.0/24 No ROA Other origin only 2 0%low visibility 2
136.238.211.0/24 No ROA RIR databaseARIN 648 96% 67
213.9.192.0/24 Valid Nonecovered by 213.9.128.0/17 600 89% 67
212.163.136.0/24 Valid Nonecovered by 212.163.0.0/16 599 89% 67
213.9.128.0/24 Valid Nonecovered by 213.9.128.0/17 599 89% 67
213.192.195.0/24 Valid Nonecovered by 213.192.192.0/18 599 89% 67
213.192.212.0/22 Valid Nonecovered by 213.192.192.0/18 599 89% 67
213.192.255.0/24 Valid Nonecovered by 213.192.192.0/18 599 89% 67
213.9.250.0/23 Valid Nonecovered by 213.9.128.0/17 598 89% 67
2001:ac0:c880::/44 Valid Nonecovered by 2001:ac0::/32 595 94% 68
2a0d:59c0::/48 Valid Nonecovered by 2a0d:59c0::/29 562 88% 68
185.203.20.0/24 Valid RIR databaseRIPE 665 99% 67
2a0d:59c1::/32 Valid RIR databaseRIPE 624 98% 69
2a0d:59c7::/32 Valid RIR databaseRIPE 624 98% 69
2001:ac0::/29 Valid RIR databaseRIPE 623 98% 69
2a0d:59c0::/29 Valid RIR databaseRIPE 623 98% 69
2a0d:59c0:2::/48 Valid RIR databaseRIPE 620 97% 69
94.198.47.0/24 Valid RIR databaseRIPE 600 89% 67
89.42.70.0/24 Valid RIR databaseRIPE 599 89% 67
89.44.150.0/24 Valid RIR databaseRIPE 599 89% 67
89.44.151.0/24 Valid RIR databaseRIPE 599 89% 67
91.132.28.0/23 Valid RIR databaseRIPE 599 89% 67
91.132.31.0/24 Valid RIR databaseRIPE 599 89% 67
92.60.160.0/20 Valid RIR databaseRIPE 599 89% 67
176.98.220.0/24 Valid RIR databaseRIPE 599 89% 67
176.98.223.0/24 Valid RIR databaseRIPE 599 89% 67
178.19.44.0/24 Valid RIR databaseRIPE 599 89% 67
178.19.47.0/24 Valid RIR databaseRIPE 599 89% 67
185.66.60.0/22 Valid RIR databaseRIPE 599 89% 67
185.66.60.0/24 Valid RIR databaseRIPE 599 89% 67
185.123.122.0/24 Valid RIR databaseRIPE 599 89% 67
185.155.64.0/24 Valid RIR databaseRIPE 599 89% 67
185.187.180.0/24 Valid RIR databaseRIPE 599 89% 67
185.187.181.0/24 Valid RIR databaseRIPE 599 89% 67
185.187.182.0/24 Valid RIR databaseRIPE 599 89% 67
185.203.21.0/24 Valid RIR databaseRIPE 599 89% 67
185.203.22.0/24 Valid RIR databaseRIPE 599 89% 67
185.224.76.0/24 Valid RIR databaseRIPE 599 89% 67
185.229.215.0/24 Valid RIR databaseRIPE 599 89% 67
185.242.175.0/24 Valid RIR databaseRIPE 599 89% 67
193.34.241.0/24 Valid RIR databaseRIPE 599 89% 67
193.186.11.0/24 Valid RIR databaseRIPE 599 89% 67
195.5.65.0/24 Valid RIR databaseRIPE 599 89% 67
195.5.67.0/24 Valid RIR databaseRIPE 599 89% 67
195.5.78.0/24 Valid RIR databaseRIPE 599 89% 67
195.5.79.0/24 Valid RIR databaseRIPE 599 89% 67
195.5.80.0/22 Valid RIR databaseRIPE 599 89% 67
195.5.84.0/22 Valid RIR databaseRIPE 599 89% 67
195.5.91.0/24 Valid RIR databaseRIPE 599 89% 67
195.5.93.0/24 Valid RIR databaseRIPE 599 89% 67
212.66.161.0/24 Valid RIR databaseRIPE 599 89% 67
212.66.162.0/23 Valid RIR databaseRIPE 599 89% 67
212.66.164.0/22 Valid RIR databaseRIPE 599 89% 67
212.66.168.0/21 Valid RIR databaseRIPE 599 89% 67
212.66.176.0/20 Valid RIR databaseRIPE 599 89% 67
212.163.5.0/24 Valid RIR databaseRIPE 599 89% 67
212.163.18.0/24 Valid RIR databaseRIPE 599 89% 67
212.163.185.0/24 Valid RIR databaseRIPE 599 89% 67
212.163.193.0/24 Valid RIR databaseRIPE 599 89% 67
213.9.142.0/23 Valid RIR databaseRIPE 599 89% 67
213.9.182.0/24 Valid RIR databaseRIPE 599 89% 67
213.9.217.0/24 Valid RIR databaseRIPE 599 89% 67
213.170.52.0/24 Valid RIR databaseRIPE 599 89% 67
45.83.50.0/24 Valid RIR databaseRIPE 598 89% 67
158.172.140.0/23 Valid RIR databaseRIPE 598 89% 67
185.155.67.0/24 Valid RIR databaseRIPE 598 89% 67
195.5.64.0/19 Valid RIR databaseRIPE 598 89% 67
195.5.66.0/24 Valid RIR databaseRIPE 598 89% 67
212.49.128.0/18 Valid RIR databaseRIPE 598 89% 67
212.163.0.0/16 Valid RIR databaseRIPE 598 89% 67
212.163.1.0/24 Valid RIR databaseRIPE 598 89% 67
212.163.91.0/24 Valid RIR databaseRIPE 598 89% 67
212.163.92.0/24 Valid RIR databaseRIPE 598 89% 67
212.163.94.0/24 Valid RIR databaseRIPE 598 89% 67
212.163.130.0/24 Valid RIR databaseRIPE 598 89% 67
212.163.225.0/24 Valid RIR databaseRIPE 598 89% 67
212.163.226.0/24 Valid RIR databaseRIPE 598 89% 67
212.163.227.0/24 Valid RIR databaseRIPE 598 89% 67
212.163.235.0/24 Valid RIR databaseRIPE 598 89% 67
212.163.240.0/20 Valid RIR databaseRIPE 598 89% 67
213.9.128.0/17 Valid RIR databaseRIPE 598 89% 67
213.9.162.0/23 Valid RIR databaseRIPE 598 89% 67
213.9.185.0/24 Valid RIR databaseRIPE 598 89% 67
213.9.186.0/24 Valid RIR databaseRIPE 598 89% 67
213.9.190.0/23 Valid RIR databaseRIPE 598 89% 67
213.9.224.0/20 Valid RIR databaseRIPE 598 89% 67
213.9.240.0/23 Valid RIR databaseRIPE 598 89% 67
213.9.244.0/24 Valid RIR databaseRIPE 598 89% 67
213.9.245.0/24 Valid RIR databaseRIPE 598 89% 67
213.9.246.0/24 Valid RIR databaseRIPE 598 89% 67
213.9.247.0/24 Valid RIR databaseRIPE 598 89% 67
213.9.248.0/24 Valid RIR databaseRIPE 598 89% 67
213.192.192.0/18 Valid RIR databaseRIPE 598 89% 67
45.83.51.0/24 Valid RIR databaseRIPE 597 89% 67
80.66.112.0/23 Valid RIR databaseRIPE 597 89% 67
80.66.114.0/24 Valid RIR databaseRIPE 597 89% 67
80.66.117.0/24 Valid RIR databaseRIPE 597 89% 67
80.66.118.0/24 Valid RIR databaseRIPE 597 89% 67
80.66.120.0/24 Valid RIR databaseRIPE 597 89% 67
80.66.121.0/24 Valid RIR databaseRIPE 597 89% 67
80.66.123.0/24 Valid RIR databaseRIPE 597 89% 67
80.66.124.0/24 Valid RIR databaseRIPE 597 89% 67
84.18.0.0/19 Valid RIR databaseRIPE 597 89% 67
80.66.115.0/24 Valid RIR databaseRIPE 596 89% 67
80.66.122.0/24 Valid RIR databaseRIPE 596 89% 67
92.60.171.0/24 Valid RIR databaseRIPE 592 88% 67
92.60.173.0/24 Valid RIR databaseRIPE 592 88% 67
92.60.174.0/24 Valid RIR databaseRIPE 592 88% 67
212.163.8.0/24 Valid RIR databaseRIPE 589 88% 67
2001:ac0::/32 Valid RIR databaseRIPE 572 90% 68
195.5.92.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
195.5.94.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS8903: RIPE::AS-LYNTIA. 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 (AS8903 isn't in the set, or no route object for AS8903 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 objectsAS8903 in itNot covered
RIPE::AS-LYNTIA RIPE 15936,734 Yes 8

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

  • ROA: none9
  • Route object: none17
  • Route object: not announced71
ChangePrefix or setDetailFull-table peers
ROA: none149.7.217.0/24No ROA covers it. Add a ROA for AS8903, maxLength 24.646 of 673
Route object: none149.7.217.0/24Route objects for it name AS202766. Add a route object with origin AS8903 in the RIR database for the space.646 of 673
ROA: none154.58.219.0/24No ROA covers it. Add a ROA for AS8903, maxLength 24.641 of 673
Route object: none154.58.219.0/24Route objects for it name AS202766. Add a route object with origin AS8903 in the RIR database for the space.641 of 673
ROA: none154.62.64.0/24No ROA covers it. Add a ROA for AS8903, maxLength 24.641 of 673
Route object: none154.62.64.0/24No route object for it. Add a route object with origin AS8903 in the RIR database for the space.641 of 673
ROA: none154.62.65.0/24No ROA covers it. Add a ROA for AS8903, maxLength 24.641 of 673
Route object: none154.62.65.0/24No route object for it. Add a route object with origin AS8903 in the RIR database for the space.641 of 673
ROA: none154.62.234.0/23No ROA covers it. Add a ROA for AS8903, maxLength 23.641 of 673
Route object: none154.62.234.0/23Route objects for it name AS202766. Add a route object with origin AS8903 in the RIR database for the space.641 of 673
ROA: none154.62.67.0/24No ROA covers it. Add a ROA for AS8903, maxLength 24.639 of 673
Route object: none154.62.67.0/24No route object for it. Add a route object with origin AS8903 in the RIR database for the space.639 of 673
ROA: none154.62.251.0/24No ROA covers it. Add a ROA for AS8903, maxLength 24.639 of 673
Route object: none154.62.251.0/24Route objects for it name AS202766. Add a route object with origin AS8903 in the RIR database for the space.639 of 673
ROA: none154.44.190.0/24No ROA covers it. Add a ROA for AS8903, maxLength 24.2 of 673
Route object: none154.44.190.0/24Route objects for it name AS202766. Add a route object with origin AS8903 in the RIR database for the space.2 of 673
ROA: none136.238.211.0/24No ROA covers it. Add a ROA for AS8903, maxLength 24.648 of 673
Route object: none213.9.192.0/24No route object for it. A route object for 213.9.128.0/17 with origin AS8903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8903 in the RIR database for the space.600 of 673
Route object: none212.163.136.0/24No route object for it. A route object for 212.163.0.0/16 with origin AS8903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8903 in the RIR database for the space.599 of 673
Route object: none213.9.128.0/24No route object for it. A route object for 213.9.128.0/17 with origin AS8903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8903 in the RIR database for the space.599 of 673
Route object: none213.192.195.0/24No route object for it. A route object for 213.192.192.0/18 with origin AS8903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8903 in the RIR database for the space.599 of 673
Route object: none213.192.212.0/22No route object for it. A route object for 213.192.192.0/18 with origin AS8903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8903 in the RIR database for the space.599 of 673
Route object: none213.192.255.0/24No route object for it. A route object for 213.192.192.0/18 with origin AS8903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8903 in the RIR database for the space.599 of 673
Route object: none213.9.250.0/23No route object for it. A route object for 213.9.128.0/17 with origin AS8903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8903 in the RIR database for the space.598 of 673
Route object: none2001:ac0:c880::/44No route object for it. A route object for 2001:ac0::/32 with origin AS8903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8903 in the RIR database for the space.595 of 636
Route object: none2a0d:59c0::/48No route object for it. A route object for 2a0d:59c0::/29 with origin AS8903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8903 in the RIR database for the space.562 of 636

Route objects not announced

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

45.83.50.0/23RIPEValid
80.66.119.0/24RIPEValid
80.66.120.0/23RIPEValid
80.66.126.0/24RIPEValid
80.66.127.0/24RIPEValid
84.18.0.0/24RIPEValid
84.18.1.0/24RIPEValid
85.209.72.0/22RIPEValid
89.45.208.0/24RIPEValid
136.238.21.0/24ARINNo ROA
158.172.142.0/24RIPEValid
176.98.220.0/22RIPEValid
178.19.34.0/24RIPEValid
178.19.35.0/24RIPEValid
178.19.45.0/24RIPEValid
178.19.46.0/24RIPEInvalid: maxLength
185.66.61.0/24RIPEValid
185.66.62.0/24RIPEValid
185.66.63.0/24RIPEValid
185.71.28.0/24RIPEValid
185.173.44.0/24RIPEValid
185.173.46.0/24RIPEValid
185.203.20.0/22RIPEValid
185.203.23.0/24RIPEValid
185.224.77.0/24RIPEValid
185.224.78.0/24RIPEValid
185.224.79.0/24RIPEValid
185.229.212.0/24RIPEInvalid: origin
185.229.213.0/24RIPEInvalid: origin
185.229.214.0/24RIPEInvalid: origin
192.88.99.0/24RIPE-NONAUTHNo ROA
193.34.240.0/24RIPEValid
193.178.212.0/24RIPEValid
193.178.218.0/24RIPEValid
193.186.1.0/24RIPEValid
194.15.140.0/24RIPEValid
194.15.146.0/24RIPEValid
194.15.182.0/24RIPEValid
194.15.195.0/24RIPEValid
195.5.64.0/24RIPEValid
195.5.84.0/24RIPEValid
195.5.85.0/24RIPEValid
195.5.86.0/24RIPEValid
195.5.87.0/24RIPEValid
212.49.128.0/19RIPEValid
212.49.128.0/23RIPEValid
212.49.160.0/19RIPEValid
212.49.189.0/24RIPEValid
212.59.192.0/19RIPEValid
212.66.160.0/19RIPENo ROA
212.66.160.0/24RIPEValid
212.66.163.0/24RIPEValid
212.80.160.0/19RIPEValid
212.80.168.0/22RIPEValid
212.163.0.0/17RIPEValid
212.163.31.0/24RIPEValid
212.163.64.0/18RIPEValid
212.163.80.0/20RIPEValid
212.163.232.0/21RIPEValid
212.163.240.0/21RIPEValid
213.9.221.0/24RIPEValid
213.9.225.0/24RIPEValid
213.9.233.0/24RIPEValid
213.170.32.0/19RIPEValid
213.192.196.0/24RIPEValid
213.192.252.0/23RIPEValid
213.192.254.0/24RIPEValid
2001:ac0:30fd::/48RIPEValid
2001:ac0:c800::/48RIPEValid
2001:ac0:c880::/48RIPEValid
2002::/16RIPE-NONAUTHNo 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.