bgpreport

Network · data from 2026-11-12

AS208537 m3networks

Registry name: m3networks M3 Groep BV, NL · PeeringDB

7IPv4 routes 100.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
0No ROA 0 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS208537, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS208537, 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.
91.230.237.0/24 Valid RIR databaseRIPE 673 100% 67
94.101.104.0/24 Valid RIR databaseRIPE 673 100% 67
192.83.120.0/24 Valid RIR databaseRIPE 673 100% 67
194.102.239.0/24 Valid RIR databaseRIPE 673 100% 67
195.114.238.0/23 Valid RIR databaseRIPE 673 100% 67
195.138.39.0/24 Valid RIR databaseRIPE 673 100% 67
213.159.24.0/23 Valid RIR databaseRIPE 673 100% 67
2a11:800::/29 Valid RIR databaseRIPE 3 0%low visibility 3

AS-SET

AS208537's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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