bgpreport

Network · data from 2026-11-12

AS31529 DENIC Anycast

Registry name: DENIC-ANYCAST-AS DENIC eG, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS31529, 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.

2a0e:dbc0:8000::/48 Valid None 636 100% 69
185.151.143.0/24 Valid RIR databaseRIPE 673 100% 67
194.0.0.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
194.246.96.0/24 Valid RIR databaseRIPE 673 100% 66
81.91.164.0/24 Valid RIR databaseRIPE 672 100% 66
194.0.11.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.151.141.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
2a02:568:fe02::/48 Valid RIR databaseRIPE 636 100% 68
2a02:56f:ff11::/48 Valid RIR databaseRIPE 636 100% 67
2001:678:2::/48 Valid RIR databaseRADB, RIPE 635 100% 69
2a02:56f:ff00::/48 Valid RIR databaseRIPE 635 100% 67
2a02:56f:ff02::/48 Valid RIR databaseRIPE 635 100% 68
2a02:56f:ff03::/48 Valid RIR databaseRIPE 635 100% 67
2a02:56f:ff04::/48 Valid RIR databaseRIPE 635 100% 69
2a02:56f:ff07::/48 Valid RIR databaseRIPE 635 100% 68
2a02:56f:ff0a::/48 Valid RIR databaseRIPE 635 100% 67
2a02:56f:ff0c::/48 Valid RIR databaseRIPE 635 100% 68
2a02:56f:ff0d::/48 Valid RIR databaseRIPE 635 100% 68
2a02:56f:ff10::/48 Valid RIR databaseRIPE 635 100% 69
2a02:56f:ff01::/48 Valid RIR databaseRIPE 634 100% 67
2a02:56f:ff05::/48 Valid RIR databaseRIPE 634 100% 69
2a02:56f:ff06::/48 Valid RIR databaseRIPE 634 100% 67
2a02:56f:ff08::/48 Valid RIR databaseRIPE 634 100% 69
2001:678:e::/48 Valid RIR databaseRIPE 632 99% 69
2a02:568:fe00::/48 Valid RIR databaseRIPE 632 99% 69
2a02:56f:ff0e::/48 Valid RIR databaseRIPE 632 99% 69
2a02:568::/48 Valid RIR databaseRIPE 630 99% 67
2a02:56f:ff09::/48 Valid RIR databaseRIPE 628 99% 67
2a02:56f:ff0b::/48 Valid RIR databaseRIPE 627 99% 67
185.151.142.0/24 Valid RIR databaseRIPE 147 22% 47
45.142.220.0/24 Valid RIR databaseRIPE 4 1%low visibility 5
45.142.223.0/24 Valid RIR databaseRIPE 4 1%low visibility 5

AS-SET

PeeringDB's irr_as_set for AS31529: AS-DENIC-ANY. 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 (AS31529 isn't in the set, or no route object for AS31529 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 objectsAS31529 in itNot covered
AS-DENIC-ANY RIPE 82117 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 7 are in fix.csv.

  • Route object: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none2a0e:dbc0:8000::/48No route object for it. Add a route object with origin AS31529 in the RIR database for the space.636 of 636

Route objects not announced

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

95.133.168.0/24RIPEValid
2a02:568:fe01::/48RIPEValid
2a02:56f:ff0f::/48RIPEValid
2a02:56f:ff12::/48RIPEValid
2a0e:dbc0::/48RIPEValid
2a0e:dbc0:3000::/48RIPEValid

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.