bgpreport

Network · data from 2026-11-12

AS50495 Web2Objects Frankfurt

Registry name: WEB2OBJECTS-EU-AS web2objects GmbH, DE · PeeringDB

25IPv4 routes 28.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
18No 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 AS50495, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS50495, 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.
45.138.116.0/23 No ROA RIR databaseRIPE 673 100% 67
45.138.118.0/23 No ROA RIR databaseRIPE 673 100% 67
45.146.28.0/23 No ROA RIR databaseRIPE 673 100% 67
45.146.30.0/23 No ROA RIR databaseRIPE 673 100% 67
45.151.160.0/23 No ROA RIR databaseRIPE 673 100% 67
45.151.162.0/23 No ROA RIR databaseRIPE 673 100% 67
193.160.236.0/24 No ROA RIR databaseRIPE 673 100% 67
193.160.237.0/24 No ROA RIR databaseRIPE 673 100% 67
193.161.2.0/24 No ROA RIR databaseRIPE 673 100% 67
193.161.3.0/24 No ROA RIR databaseRIPE 673 100% 67
194.113.112.0/24 No ROA RIR databaseRIPE 673 100% 67
194.113.113.0/24 No ROA RIR databaseRIPE 673 100% 67
194.113.118.0/24 No ROA RIR databaseRIPE 673 100% 67
194.113.119.0/24 No ROA RIR databaseRIPE 673 100% 67
45.87.69.0/24 No ROA RIR databaseRIPE 672 100% 67
45.87.70.0/24 No ROA RIR databaseRIPE 672 100% 67
96.125.154.0/23 No ROA RIR databaseRIPE 670 100% 67
96.125.156.0/22 No ROA RIR databaseRIPE 670 100% 67
77.83.232.0/22 Valid RIR databaseRIPE 673 100% 67
91.204.48.0/23 Valid RIR databaseRIPE 673 100% 67
91.204.50.0/24 Valid RIR databaseRIPE 673 100% 67
91.223.99.0/24 Valid RIR databaseRIPE 673 100% 67
91.223.102.0/24 Valid RIR databaseRIPE 673 100% 67
91.223.126.0/24 Valid RIR databaseRIPE 673 100% 67
194.39.32.0/22 Valid RIR databaseRIPE 673 100% 67
2a06:ef40::/32 Valid RIR databaseRIPE 634 100% 67

AS-SET

AS50495's PeeringDB record names no 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 18 are in fix.csv.

  • ROA: none18
ChangePrefix or setDetailFull-table peers
ROA: none45.138.116.0/23No ROA covers it. Add a ROA for AS50495, maxLength 23.673 of 673
ROA: none45.138.118.0/23No ROA covers it. Add a ROA for AS50495, maxLength 23.673 of 673
ROA: none45.146.28.0/23No ROA covers it. Add a ROA for AS50495, maxLength 23.673 of 673
ROA: none45.146.30.0/23No ROA covers it. Add a ROA for AS50495, maxLength 23.673 of 673
ROA: none45.151.160.0/23No ROA covers it. Add a ROA for AS50495, maxLength 23.673 of 673
ROA: none45.151.162.0/23No ROA covers it. Add a ROA for AS50495, maxLength 23.673 of 673
ROA: none193.160.236.0/24No ROA covers it. Add a ROA for AS50495, maxLength 24.673 of 673
ROA: none193.160.237.0/24No ROA covers it. Add a ROA for AS50495, maxLength 24.673 of 673
ROA: none193.161.2.0/24No ROA covers it. Add a ROA for AS50495, maxLength 24.673 of 673
ROA: none193.161.3.0/24No ROA covers it. Add a ROA for AS50495, maxLength 24.673 of 673
ROA: none194.113.112.0/24No ROA covers it. Add a ROA for AS50495, maxLength 24.673 of 673
ROA: none194.113.113.0/24No ROA covers it. Add a ROA for AS50495, maxLength 24.673 of 673
ROA: none194.113.118.0/24No ROA covers it. Add a ROA for AS50495, maxLength 24.673 of 673
ROA: none194.113.119.0/24No ROA covers it. Add a ROA for AS50495, maxLength 24.673 of 673
ROA: none45.87.69.0/24No ROA covers it. Add a ROA for AS50495, maxLength 24.672 of 673
ROA: none45.87.70.0/24No ROA covers it. Add a ROA for AS50495, maxLength 24.672 of 673
ROA: none96.125.154.0/23No ROA covers it. Add a ROA for AS50495, maxLength 23.670 of 673
ROA: none96.125.156.0/22No ROA covers it. Add a ROA for AS50495, maxLength 22.670 of 673

Route objects not announced

Every route object with origin AS50495 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.