bgpreport

Network · data from 2026-11-12

AS208681 IDEALO-AS Idealo Internet GmbH

Registry name: IDEALO-AS Idealo Internet GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208681, 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.
45.89.128.0/22 Valid Other IRR onlyRADB 673 100% 67
2a0b:a200::/48 Valid Other IRR onlyRADB 636 100% 67
2a0b:a200:1::/48 Valid Other IRR onlyRADB 636 100% 67
2a0b:a200:2::/48 Valid Other IRR onlyRADB 636 100% 67
2a0b:a200:3::/48 Valid Other IRR onlyRADB 636 100% 67
2a0b:a200:4::/48 Valid Other IRR onlyRADB 636 100% 67
2a0b:a200:5::/48 Valid Other IRR onlyRADB 636 100% 67

AS-SET

AS208681 isn't in PeeringDB, where networks name their 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 14 are in fix.csv.

  • Route object: RIR7
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: RIR45.89.128.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2a0b:a200::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2a0b:a200:1::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2a0b:a200:2::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2a0b:a200:3::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2a0b:a200:4::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2a0b:a200:5::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

2a0b:a200::/29RIPENo ROA
2a0b:a200:6::/48RADBValid
2a0b:a200:7::/48RADBValid
2a0b:a200:8::/48RADBValid
2a0b:a200:9::/48RADBValid
2a0b:a200:a::/48RADBValid
2a0b:a200:b::/48RADBValid

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.