Network · data from 2026-11-12
AS61079 DIGI IT
Registry name: DIGI-IT Digi Italy S.R.L., IT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61079, 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.19.164.0/24 | Valid | Nonecovered by 185.19.164.0/23 | 669 99% |
| 185.19.165.0/24 | Valid | Nonecovered by 185.19.164.0/23 | 669 99% |
| 185.19.166.0/24 | Valid | Nonecovered by 185.19.166.0/23 | 669 99% |
| 185.19.167.0/24 | Valid | Nonecovered by 185.19.166.0/23 | 669 99% |
| 46.102.64.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 89.46.12.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 93.113.40.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 2a04:1240::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS61079: AS61079:AS-DIGIIT. 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 (AS61079 isn't in the set, or no route object for AS61079 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 | AS61079 in it | Not covered |
|---|---|---|---|---|---|
| AS61079:AS-DIGIIT | RIPE | 1 | 1 | 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 7 are in fix.csv.
- Route object: none4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.19.164.0/24 | No route object for it. A route object for 185.19.164.0/23 with origin AS61079 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61079 in the RIR database for the space. |
| Route object: none | 185.19.165.0/24 | No route object for it. A route object for 185.19.164.0/23 with origin AS61079 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61079 in the RIR database for the space. |
| Route object: none | 185.19.166.0/24 | No route object for it. A route object for 185.19.166.0/23 with origin AS61079 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61079 in the RIR database for the space. |
| Route object: none | 185.19.167.0/24 | No route object for it. A route object for 185.19.166.0/23 with origin AS61079 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61079 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61079 whose prefix no peer sees AS61079 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.19.164.0/22 | RIPE | No ROA |
| 185.19.164.0/23 | RIPE | Valid |
| 185.19.166.0/23 | 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.