bgpreport

Network · data from 2026-11-12

AS49028 D-LAKE AS49028

Registry name: D-LAKE D-LAKE SAS, FR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS49028, 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.
185.252.236.6/32 Invalid: maxLength Nonecovered by 185.252.236.0/22 2 0%low visibility 1
2.59.188.0/22 Valid RIR databaseRIPE 663 99% 66
45.151.8.0/22 Valid RIR databaseRIPE 663 99% 66
185.125.141.0/24 Valid RIR databaseRIPE 663 99% 66
185.153.136.0/22 Valid RIR databaseRIPE 663 99% 66
185.165.193.0/24 Valid RIR databaseRIPE 663 99% 66
185.170.20.0/22 Valid RIR databaseRIPE 663 99% 66
185.252.236.0/22 Valid RIR databaseRIPE 663 99% 66
193.203.52.0/22 Valid RIR databaseRIPE 663 99% 66
2a09:f7c0::/29 Valid RIR databaseRIPE 625 98% 68
2a0a:300::/29 Valid RIR databaseRIPE 625 98% 68
2a0a:6d80::/29 Valid RIR databaseRIPE 625 98% 68
2a0c:2dc0::/29 Valid RIR databaseRIPE 625 98% 68

AS-SET

PeeringDB's irr_as_set for AS49028: RIPE::AS-D-LAKE. 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 (AS49028 isn't in the set, or no route object for AS49028 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 objectsAS49028 in itNot covered
RIPE::AS-D-LAKE RIPE 15272 Yes 1

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.

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength185.252.236.6/32ROA 185.252.236.0/22 AS49028 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 185.252.236.6/32.2 of 673
Route object: none185.252.236.6/32No route object for it. A route object for 185.252.236.0/22 with origin AS49028 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS49028 in the RIR database for the space.2 of 673

Route objects not announced

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

193.203.52.0/24RIPEInvalid: maxLength
193.203.55.0/24RIPEInvalid: maxLength

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.