Routing security
AS198013 IPKOM Ipkom Srl
Hosting RIPE Network Services
Announcements
What this network originates
Every prefix observed with AS198013 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 94.185.97.0/24 | RPKI valid | IRR | 53 |
| 94.185.98.0/24 | RPKI valid | IRR | 53 |
| 94.185.99.0/24 | RPKI valid | IRR | 53 |
| 94.185.100.0/24 | RPKI valid | IRR | 53 |
| 94.185.101.0/24 | RPKI valid | IRR | 53 |
| 94.185.103.0/24 | RPKI valid | IRR covering | 53 |
| 94.185.104.0/24 | RPKI valid | IRR | 52 |
| 94.185.105.0/24 | RPKI valid | IRR | 52 |
| 94.185.107.0/24 | RPKI valid | IRR | 52 |
| 94.185.108.0/24 | RPKI valid | IRR | 53 |
| 94.185.109.0/24 | RPKI valid | IRR | 53 |
| 94.185.110.0/24 | RPKI valid | IRR covering | 53 |
| 94.185.112.0/24 | RPKI valid | IRR | 53 |
| 94.185.113.0/24 | RPKI valid | IRR covering | 53 |
| 94.185.114.0/24 | RPKI valid | IRR | 53 |
| 94.185.123.0/24 | RPKI valid | IRR covering | 53 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS198013 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 94.185.96.0/19 | /19 | RIPENCC |
| 94.185.97.0/24 | /24 | RIPENCC |
| 94.185.98.0/24 | /24 | RIPENCC |
| 94.185.99.0/24 | /24 | RIPENCC |
| 94.185.100.0/24 | /24 | RIPENCC |
| 94.185.101.0/24 | /24 | RIPENCC |
| 94.185.102.0/24 | /24 | RIPENCC |
| 94.185.103.0/24 | /24 | RIPENCC |
| 94.185.104.0/22 | /22 | RIPENCC |
| 94.185.104.0/24 | /24 | RIPENCC |
| 94.185.105.0/24 | /24 | RIPENCC |
| 94.185.106.0/24 | /24 | RIPENCC |
| 94.185.107.0/24 | /24 | RIPENCC |
| 94.185.108.0/24 | /24 | RIPENCC |
| 94.185.109.0/24 | /24 | RIPENCC |
| 94.185.110.0/24 | /24 | RIPENCC |
| 94.185.112.0/24 | /24 | RIPENCC |
| 94.185.113.0/24 | /24 | RIPENCC |
| 94.185.114.0/24 | /24 | RIPENCC |
| 94.185.116.0/24 | /24 | RIPENCC |
| 94.185.123.0/24 | /24 | RIPENCC |
| 2a03:4580::/32 | /32 | 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 |
|---|---|---|---|
| AS174 | Cogent Communications, LLC | Declared | Observed |
| AS3269 | Telecom Italia S.p.A. | Declared | Observed |
| AS3302 | Retelit Digital Services S.p.A. | Declared | not observed |
| AS30848 | UNIDATA S.p.A. | Declared | not observed |
| AS41327 | Fiber Telecom S.p.A. | Declared | Observed |
| AS197589 | Alfanews S.r.l. | Declared | not 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 AS198013 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 |
|---|---|---|---|---|---|
| 94.185.96.0/19 | RIPE | IPKOM | IPKOM-MNT | 2011-09-16 | Not announced |
| 94.185.96.0/20 | RIPE | — | IPKOM-MNT | 2020-09-28 | Not announced |
| 94.185.96.0/22 | RIPE | IPKOM Servers | IPKOM-MNT | 2013-06-20 | Not announced |
| 94.185.96.0/24 | RIPE | — | IPKOM-MNT | 2017-02-05 | Not announced |
| 94.185.100.0/22 | RIPE | IPKOM Servers altri servizi | IPKOM-MNT | 2013-06-20 | Not announced |
| 94.185.104.0/22 | RIPE | — | IPKOM-MNT | 2019-01-09 | Not announced |
| 94.185.106.0/24 | RIPE | — | IPKOM-MNT | 2023-08-02 | Not announced |
| 94.185.116.0/24 | RIPE | — | IPKOM-MNT | 2024-03-14 | Not announced |
| 2a03:4580::/32 | RIPE | IPKOM | IPKOM-MNT | 2011-09-16 | Not announced |
| 94.185.97.0/24 | RIPE | — | IPKOM-MNT | 2017-02-03 | Announced |
| 94.185.98.0/24 | RIPE | — | IPKOM-MNT | 2017-02-03 | Announced |
| 94.185.99.0/24 | RIPE | — | IPKOM-MNT | 2017-02-03 | Announced |
| 94.185.100.0/24 | RIPE | — | IPKOM-MNT | 2017-02-03 | Announced |
| 94.185.101.0/24 | RIPE | — | IPKOM-MNT | 2017-02-03 | Announced |
| 94.185.104.0/24 | RIPE | — | IPKOM-MNT | 2023-08-02 | Announced |
| 94.185.105.0/24 | RIPE | — | IPKOM-MNT | 2023-08-02 | Announced |
| 94.185.107.0/24 | RIPE | — | IPKOM-MNT | 2023-08-02 | Announced |
| 94.185.108.0/24 | RIPE | — | IPKOM-MNT | 2017-01-05 | Announced |
| 94.185.109.0/24 | RIPE | — | IPKOM-MNT | 2017-01-05 | Announced |
| 94.185.112.0/24 | RIPE | — | IPKOM-MNT | 2019-01-10 | Announced |
| 94.185.114.0/24 | RIPE | — | IPKOM-MNT | 2026-04-07 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS198013 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-IPKOM | PeeringDB | Declared by the operator as its own set |
AS-3302-CUST | RIPE | Lists AS198013 as a direct member |
AS-IBSCUST | RIPE | Lists AS198013 as a direct member |
AS-IPKOM | RIPE | Lists AS198013 as a direct member |
AS-LARGABANDA | RIPE | Lists AS198013 as a direct member |
AS-UDOS | RADB | Lists AS198013 as a direct member |
AS3302:AS-CUST | RIPE | Lists AS198013 as a direct member |
AS41327:AS-CUSTOMERS | RIPE | Lists AS198013 as a direct member |
RPKI from rpki-client, validated 2026-11-05 13:06 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-11-05. Cross-check on bgp.he.net.