Network · data from 2026-11-12
AS51337 DEBACOM
Registry name: DEBACOM-ASN DEBACOM Sp. z o.o., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51337, 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.
| 178.215.205.167/32 | Invalid: maxLength | Nonecovered by 178.215.192.0/20 | 0 0%low visibility |
| 2a02:c47:1c::/48 | No ROA | RIR databaseRIPE | 635 100% |
| 178.212.40.0/21 | Valid | RIR databaseRIPE | 671 100% |
| 178.215.192.0/20 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS51337: AS-DEBACOM. 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 (AS51337 isn't in the set, or no route object for AS51337 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.
| Name | Database | ASNs | Sets | AS51337 in it | Not covered |
|---|---|---|---|---|---|
| AS-DEBACOM | RIPE | 2 | 1 | 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
- ROA: none1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 178.215.205.167/32 | ROA 178.215.192.0/20 AS51337 has maxLength 20; the route is a /32. Raise the maxLength, or add a ROA for 178.215.205.167/32. |
| Route object: none | 178.215.205.167/32 | No route object for it. A route object for 178.215.192.0/20 with origin AS51337 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS51337 in the RIR database for the space. |
| ROA: none | 2a02:c47:1c::/48 | No ROA covers it. Add a ROA for AS51337, maxLength 48. |
Route objects not announced
Route objects with origin AS51337 whose prefix no peer sees AS51337 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a10:f781:10:387::/64 | RIPE | No ROA |
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.