bgpreport

Network · data from 2026-11-12

AS8495 INTERNET AG Global Network

Registry name: INTERNET_AG INTERNET AG Global Network, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8495, 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.
194.187.240.0/22 No ROA RIR databaseRIPE 673 100% 66
77.81.74.0/24 No ROA RIR databaseRIPE 672 100% 66
195.34.161.0/24 Valid Nonecovered by 195.34.160.0/19 673 100% 67
89.146.248.0/24 Valid Nonecovered by 89.146.192.0/18 670 100% 67
62.116.150.0/23 Valid RIR databaseRIPE 673 100% 66
62.116.152.0/23 Valid RIR databaseRIPE 673 100% 66
85.209.200.0/22 Valid RIR databaseRIPE 673 100% 66
89.146.192.0/18 Valid RIR databaseRIPE 673 100% 66
185.67.36.0/23 Valid RIR databaseRIPE 673 100% 67
193.25.172.0/24 Valid RIR databaseRIPE 673 100% 66
195.34.160.0/19 Valid RIR databaseRIPE 673 100% 66
45.135.106.0/24 Valid RIR databaseRIPE 672 100% 66
2a0e:6b40:20::/48 Valid RIR databaseRIPE 634 100% 67
2a01:130::/32 Valid RIR databaseRIPE 627 99% 67
2a05:bc0:1000::/47 Valid RIR databaseRIPE 627 99% 67
2a05:bc0:1000::/48 Valid RIR databaseRIPE 627 99% 67
2a05:bc0:1001::/48 Valid RIR databaseRIPE 627 99% 67
89.146.236.0/23 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS8495'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 13 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none194.187.240.0/22No ROA covers it. Add a ROA for AS8495, maxLength 22.673 of 673
ROA: none77.81.74.0/24No ROA covers it. Add a ROA for AS8495, maxLength 24.672 of 673
Route object: none195.34.161.0/24No route object for it. A route object for 195.34.160.0/19 with origin AS8495 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8495 in the RIR database for the space.673 of 673
Route object: none89.146.248.0/24No route object for it. A route object for 89.146.192.0/18 with origin AS8495 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8495 in the RIR database for the space.670 of 673

Route objects not announced

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

62.116.150.0/24RIPEValid
89.146.237.0/24RIPEValid
185.67.36.0/24RIPEValid
185.67.37.0/24RIPEValid
194.187.240.0/23RIPENo ROA
194.187.242.0/23RIPENo ROA
195.34.182.0/24RIPEValid
195.47.195.0/24RIPENo ROA
2a05:bc0::/32RIPEInvalid: origin

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.