bgpreport

Network · data from 2026-11-12

AS201896 MEDIACTIVE 24/7

Registry name: ASN-MEDIACTIVE-24-7 MEDIACTIVE 24/7 SARL, FR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS201896, 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.
2a02:68e0::/32 Valid None 605 95% 67
185.59.40.0/22 Valid RIR databaseRIPE 672 100% 67
185.59.42.0/24 Valid RIR databaseRIPE 672 100% 67
185.59.40.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS201896'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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none2a02:68e0::/32No route object for it. Add a route object with origin AS201896 in the RIR database for the space.605 of 636

Route objects not announced

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