bgpreport

Network · data from 2026-11-12

AS209823 Enki Multimedia

Registry name: ENKI-AS Enki Multimedia EURL, FR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS209823, 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.
2a12:5541:200::/48 Valid Nonecovered by 2a12:5540::/29 2 0%low visibility 2
2a12:5542:10::/48 Valid Nonecovered by 2a12:5542::/32 2 0%low visibility 2
2a12:5542:4001::/48 Valid Nonecovered by 2a12:5542::/32 2 0%low visibility 2
195.24.245.0/24 Valid RIR databaseRIPE 673 100% 66
5.144.32.0/24 Valid RIR databaseRIPE 669 99% 66
5.144.33.0/24 Valid RIR databaseRIPE 669 99% 66
2a12:5541:1::/48 Valid RIR databaseRIPE 636 100% 69
2a12:5541:2::/48 Valid RIR databaseRIPE 636 100% 69
2a12:5541:100::/48 Valid RIR databaseRIPE 636 100% 69
2a12:5541:331::/48 Valid RIR databaseRIPE 636 100% 69
2a12:5542::/32 Valid RIR databaseRIPE 636 100% 69
2a12:5541:a::/48 Valid RIR databaseRIPE 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS209823: RIPE::AS209823:AS-ENKI. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS209823 isn't in the set, or no route object for AS209823 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS209823 in itNot covered
RIPE::AS209823:AS-ENKI RIPE 1210 Yes 0

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 4 are in fix.csv.

  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2a12:5541:200::/48No route object for it. A route object for 2a12:5540::/29 with origin AS209823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209823 in the RIR database for the space.2 of 636
Route object: none2a12:5542:10::/48No route object for it. A route object for 2a12:5542::/32 with origin AS209823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209823 in the RIR database for the space.2 of 636
Route object: none2a12:5542:4001::/48No route object for it. A route object for 2a12:5542::/32 with origin AS209823 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209823 in the RIR database for the space.2 of 636

Route objects not announced

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

2a12:5540::/29RIPENo ROA

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.