bgpreport

Network · data from 2026-11-12

AS208559 IPB CDN

Registry name: ipbcdn IPB Internet Provider in Berlin GmbH, DE · PeeringDB

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

Announced routes

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

2.57.160.0/23 Valid None 673 100% 66

AS-SET

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

  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none2.57.160.0/23No route object for it. Add a route object with origin AS208559 in the RIR database for the space.673 of 673

Route objects not announced

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

2a02:f28:23::/48RIPEValid
2a09:ce40::/29RIPEValid
2a09:ce40::/40RIPEInvalid: 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.