Network · data from 2026-11-12
AS199439 Dreamlink sp. z o.o.
Registry name: DREAMLINK-AS Dreamlink sp. z o.o., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS199439, 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.86.32.0/24 | No ROA | None | 2 0%low visibility |
| 93.113.182.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 107.6.104.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 141.11.102.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
AS-SET
AS199439'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.
- ROA: none1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.86.32.0/24 | No ROA covers it. Add a ROA for AS199439, maxLength 24. |
| Route object: none | 45.86.32.0/24 | No route object for it. Add a route object with origin AS199439 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS199439 whose prefix no peer sees AS199439 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.46.127.0/24 | RIPE | Valid |
| 87.76.182.0/24 | RADB, RIPE | Valid |
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.