bgpreport

Network · data from 2026-11-12

AS25181 EU-SONY

Registry name: EU-SONY Sony Europe B.V., NL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25181, 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.
192.16.134.0/24 No ROA RIR databaseRIPE 518 77% 66
192.16.135.0/24 No ROA RIR databaseRIPE 518 77% 66
192.16.136.0/24 No ROA RIR databaseRIPE 518 77% 66
195.2.32.0/22 Valid Nonecovered by 195.2.32.0/19 673 100% 67
37.139.152.0/21 Valid RIR databaseRIPE 673 100% 67
195.2.32.0/19 Valid RIR databaseRIPE 673 100% 67
195.2.36.0/22 Valid RIR databaseRIPE 673 100% 67
195.2.40.0/23 Valid RIR databaseRIPE 673 100% 67
195.2.40.0/24 Valid RIR databaseRIPE 673 100% 67
2a00:1310::/32 Valid RIR databaseRIPE 635 100% 68
2a00:1310:110::/48 Valid RIR databaseRIPE 635 100% 68
2a00:1310:3fae::/48 Valid RIR databaseRIPE 635 100% 68
2a00:1310:fffe::/48 Valid RIR databaseRIPE 635 100% 68
2a00:1310:802::/48 Valid RIR databaseRIPE 634 100% 67
2a00:1310:301::/48 Valid RIR databaseRIPE 491 77% 67

AS-SET

AS25181'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 12 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none192.16.134.0/24No ROA covers it. Add a ROA for AS25181, maxLength 24.518 of 673
ROA: none192.16.135.0/24No ROA covers it. Add a ROA for AS25181, maxLength 24.518 of 673
ROA: none192.16.136.0/24No ROA covers it. Add a ROA for AS25181, maxLength 24.518 of 673
Route object: none195.2.32.0/22No route object for it. A route object for 195.2.32.0/19 with origin AS25181 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25181 in the RIR database for the space.673 of 673

Route objects not announced

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

195.2.36.0/23RIPEValid
195.2.38.0/23RIPEValid
195.2.41.0/24RIPEValid
195.2.42.0/24RIPEValid
195.2.43.0/24RIPEValid
2a00:1310:3fab::/48RIPEValid
2a00:1310:3fac::/48RIPEValid
2a00:96c0::/32RIPEValid

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.