Network · data from 2026-11-12
AS249 PACKETSTAR
Registry name: PACKETSTAR - IDDQD-AS, EU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS249, 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.
| 185.116.108.0/22 | No ROA | RIR databaseRIPE | 670 100% |
| 2a06:7e07::/32 | No ROA | RIR databaseRIPE | 634 100% |
| 2a06:7e00::/29 | No ROA | RIR databaseRIPE | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS249: RIPE::AS249:AS-CUSTOMERS. 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 (AS249 isn't in the set, or no route object for AS249 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 | AS249 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS249:AS-CUSTOMERS | RIPElists itself further down2 member sets in no database: AS-AVSISP, AS209697:AS-CONE | 20 | 12 | Yes | 0 |
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 9 are in fix.csv.
- ROA: none3
- AS-SET: missing member2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.116.108.0/22 | No ROA covers it. Add a ROA for AS249, maxLength 22. |
| ROA: none | 2a06:7e07::/32 | No ROA covers it. Add a ROA for AS249, maxLength 32. |
| ROA: none | 2a06:7e00::/29 | No ROA covers it. Add a ROA for AS249, maxLength 29. |
| AS-SET: missing member | RIPE::AS249:AS-CUSTOMERS | AS249:AS-CUSTOMERS (RIPE) lists AS-AVSISP; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS249:AS-CUSTOMERS | AS249:AS-CUSTOMERS (RIPE) lists AS209697:AS-CONE; no IRR database read has it. |
Route objects not announced
Route objects with origin AS249 whose prefix no peer sees AS249 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.116.108.0/24 | RIPE | No ROA |
| 2a06:7e00::/32 | RIPE | No ROA |
| 2a06:7e01::/32 | RIPE | No ROA |
| 2a06:7e02::/32 | 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.