Routing security
AS39719 LIGURIADIGITALE_AS
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS39719 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 62.177.16.0/21 | RPKI valid | IRR | 52 |
| 62.177.16.0/22 | RPKI valid | IRR covering | 16 |
| 62.177.20.0/22 | RPKI valid | IRR covering | 16 |
| 62.177.24.0/21 | RPKI valid | IRR | 53 |
| 62.177.24.0/24 | RPKI valid | IRR | 16 |
| 62.177.25.0/24 | RPKI valid | IRR | 16 |
| 62.177.26.0/24 | RPKI valid | IRR | 16 |
| 62.177.27.0/24 | RPKI valid | IRR | 16 |
| 62.177.28.0/24 | RPKI valid | IRR | 16 |
| 62.177.29.0/24 | RPKI valid | IRR | 16 |
| 62.177.30.0/24 | RPKI valid | IRR | 16 |
| 62.177.31.0/24 | RPKI valid | IRR | 16 |
| 81.23.80.0/20 | RPKI valid | IRR | 52 |
| 81.23.80.0/21 | RPKI valid | IRR covering | 52 |
| 81.23.80.0/22 | RPKI valid | IRR | 51 |
| 81.23.84.0/22 | RPKI valid | IRR | 51 |
| 81.23.88.0/21 | RPKI valid | IRR covering | 52 |
| 81.23.88.0/22 | RPKI valid | IRR | 51 |
| 81.23.92.0/22 | RPKI valid | IRR | 51 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS39719 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 62.177.16.0/21 | /24 | RIPENCC |
| 62.177.16.0/22 | /22 | RIPENCC |
| 62.177.20.0/22 | /22 | RIPENCC |
| 62.177.24.0/21 | /21 | RIPENCC |
| 62.177.24.0/24 | /24 | RIPENCC |
| 62.177.25.0/24 | /24 | RIPENCC |
| 62.177.26.0/24 | /24 | RIPENCC |
| 62.177.27.0/24 | /24 | RIPENCC |
| 62.177.28.0/24 | /24 | RIPENCC |
| 62.177.29.0/24 | /24 | RIPENCC |
| 62.177.30.0/24 | /24 | RIPENCC |
| 62.177.31.0/24 | /24 | RIPENCC |
| 81.23.80.0/20 | /22 | RIPENCC |
| 81.23.80.0/21 | /21 | RIPENCC |
| 81.23.80.0/22 | /22 | RIPENCC |
| 81.23.84.0/22 | /22 | RIPENCC |
| 81.23.84.0/23 | /23 | RIPENCC |
| 81.23.84.0/24 | /24 | RIPENCC |
| 81.23.88.0/21 | /21 | RIPENCC |
| 81.23.88.0/22 | /22 | RIPENCC |
| 81.23.92.0/22 | /22 | RIPENCC |
| 2a12:1d40::/29 | /29 | RIPENCC |
| 2a12:1d40:1::/48 | /48 | RIPENCC |
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
This network has signed an ASPA record naming its transit providers. Each is compared against the upstreams observed in routing paths.
| AS | Network | ASPA | Routing paths |
|---|---|---|---|
| AS1267 | WIND TRE S.P.A. | Declared | not observed |
| AS3302 | Retelit Digital Services S.p.A. | Declared | Observed |
| AS12874 | Fastweb SpA | Declared | not observed |
| AS16004 | Milan Internet eXchange | Declared | not observed |
| AS61968 | unnamed | Declared | not observed |
| AS200199 | unnamed | Declared | not observed |
| AS9002 | RETN Limited | not declared | Observed |
| AS6939 | Hurricane Electric LLC | not declared | Observed |
| AS24482 | SG.GS | not declared | Observed |
| AS59919 | Brainbox S.r.l. | not declared | Observed |
| AS29075 | IELO-LIAZO SERVICES SAS | not declared | Observed |
| AS31543 | myNet GmbH | not declared | Observed |
An observed upstream that is not declared is not necessarily a leak: our upstream inference cannot tell a transit provider from a peer seen in the same position. A declared provider that is never observed is usually a backup path.
IRR
Registered route objects
Route objects naming AS39719 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.
| Prefix | Source | Description | Maintainer | Changed | Routing |
|---|---|---|---|---|---|
| 81.23.81.0/24 | RIPE | — | MNT-DATASIEL | 2019-02-07 | Not announced |
| 81.23.82.0/24 | RIPE | — | MNT-DATASIEL | 2021-06-03 | Not announced |
| 81.23.83.0/24 | RIPE | — | MNT-DATASIEL | 2019-02-07 | Not announced |
| 81.23.84.0/23 | RIPE | — | MNT-DATASIEL | 2022-06-07 | Not announced |
| 81.23.84.0/24 | RIPE | — | MNT-DATASIEL | 2021-06-03 | Not announced |
| 81.23.85.0/24 | RIPE | — | MNT-DATASIEL | 2021-06-03 | Not announced |
| 81.23.86.0/24 | RIPE | — | MNT-DATASIEL | 2021-06-03 | Not announced |
| 81.23.87.0/24 | RIPE | — | MNT-DATASIEL | 2021-06-03 | Not announced |
| 81.23.88.0/24 | RIPE | — | MNT-DATASIEL | 2021-06-03 | Not announced |
| 81.23.89.0/24 | RIPE | — | MNT-DATASIEL | 2021-06-03 | Not announced |
| 81.23.90.0/24 | RIPE | — | MNT-DATASIEL | 2021-06-03 | Not announced |
| 81.23.91.0/24 | RIPE | — | MNT-DATASIEL | 2021-06-03 | Not announced |
| 81.23.92.0/24 | RIPE | — | MNT-DATASIEL | 2021-06-03 | Not announced |
| 81.23.93.0/24 | RIPE | — | MNT-DATASIEL | 2021-06-03 | Not announced |
| 81.23.94.0/24 | RIPE | — | MNT-DATASIEL | 2021-06-03 | Not announced |
| 81.23.95.0/24 | RIPE | — | MNT-DATASIEL | 2021-06-03 | Not announced |
| 2a12:1d40::/29 | RIPE | — | MNT-DATASIEL | 2022-05-30 | Not announced |
| 2a12:1d40:1::/48 | RIPE | — | MNT-DATASIEL | 2022-05-30 | Not announced |
| 62.177.16.0/21 | RIPE | — | MNT-DATASIEL | 2024-09-06 | Announced |
| 62.177.24.0/21 | RIPE | — | MNT-DATASIEL | 2022-10-24 | Announced |
| 62.177.24.0/24 | RIPE | — | MNT-DATASIEL | 2022-11-28 | Announced |
| 62.177.25.0/24 | RIPE | — | MNT-DATASIEL | 2022-11-28 | Announced |
| 62.177.26.0/24 | RIPE | — | MNT-DATASIEL | 2022-11-28 | Announced |
| 62.177.27.0/24 | RIPE | — | MNT-DATASIEL | 2022-11-28 | Announced |
| 62.177.28.0/24 | RIPE | — | MNT-DATASIEL | 2022-11-28 | Announced |
| 62.177.29.0/24 | RIPE | — | MNT-DATASIEL | 2022-11-28 | Announced |
| 62.177.30.0/24 | RIPE | — | MNT-DATASIEL | 2022-11-28 | Announced |
| 62.177.31.0/24 | RIPE | — | MNT-DATASIEL | 2022-11-28 | Announced |
| 81.23.80.0/20 | RIPE | Datasiel SpA Block | MNT-DATASIEL | 2007-03-28 | Announced |
| 81.23.80.0/22 | RIPE | — | MNT-DATASIEL | 2021-12-09 | Announced |
| 81.23.84.0/22 | RIPE | — | MNT-DATASIEL | 2021-12-09 | Announced |
| 81.23.88.0/22 | RIPE | — | MNT-DATASIEL | 2021-12-09 | Announced |
| 81.23.92.0/22 | RIPE | — | MNT-DATASIEL | 2021-12-09 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS39719 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-FASTWEB | RIPE | Lists AS39719 as a direct member |
AS-IBSCUST | RIPE | Lists AS39719 as a direct member |
AS-INFOSTRADA | RIPE | Lists AS39719 as a direct member |
AS-PANSERVICE | RIPE | Lists AS39719 as a direct member |
AS-RETN | RIPE | Lists AS39719 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS39719 as a direct member |
AS-UDOS | RADB | Lists AS39719 as a direct member |
AS-WINDTRE | RIPE | Lists AS39719 as a direct member |
AS208920:AS-CUSTOMERS | RIPE | Lists AS39719 as a direct member |
AS3302:AS-CUST | RIPE | Lists AS39719 as a direct member |
RPKI from rpki-client, validated 2026-10-21 12:00 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-21. Cross-check on bgp.he.net.