Routing security
AS20912 ASN-PANSERVICE
Residential RIPE Cable/DSL/ISP
Announcements
What this network originates
Every prefix observed with AS20912 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 46.102.96.0/22 | RPKI valid | IRR | 51 |
| 77.39.192.0/20 | RPKI valid | IRR | 51 |
| 77.39.216.0/22 | RPKI valid | IRR | 51 |
| 85.119.176.0/21 | RPKI valid | IRR | 51 |
| 185.109.188.0/22 | RPKI valid | IRR | 51 |
| 193.36.108.0/22 | RPKI valid | IRR | 51 |
| 212.66.96.0/19 | RPKI valid | IRR | 51 |
| 212.66.118.0/24 | RPKI valid | IRR covering | 51 |
| 212.66.119.0/24 | RPKI valid | IRR covering | 51 |
| 212.66.120.0/22 | RPKI valid | IRR | 51 |
| 212.66.120.0/24 | RPKI valid | IRR covering | 51 |
| 212.66.121.0/24 | RPKI valid | IRR covering | 51 |
| 212.66.122.0/23 | RPKI valid | IRR covering | 51 |
| 212.66.122.0/24 | RPKI valid | IRR covering | 51 |
| 2001:40d0::/32 | RPKI valid | IRR | 35 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS20912 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 46.102.96.0/22 | /22 | RIPENCC |
| 77.39.192.0/20 | /24 | RIPENCC |
| 77.39.216.0/22 | /24 | RIPENCC |
| 85.119.176.0/21 | /24 | RIPENCC |
| 185.109.188.0/22 | /24 | RIPENCC |
| 193.36.108.0/22 | /22 | RIPENCC |
| 193.36.108.0/24 | /24 | RIPENCC |
| 193.36.109.0/24 | /24 | RIPENCC |
| 193.36.110.0/24 | /24 | RIPENCC |
| 193.36.111.0/24 | /24 | RIPENCC |
| 212.66.96.0/19 | /24 | RIPENCC |
| 2001:40d0::/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 |
| AS3257 | GTT Communications Inc. | Declared | Observed |
| AS9002 | RETN Limited | Declared | Observed |
| AS6939 | Hurricane Electric LLC | not declared | Observed |
| AS24482 | SG.GS | not declared | Observed |
| AS3303 | Swisscom (Schweiz) AG | not declared | Observed |
| AS59919 | Brainbox S.r.l. | not declared | Observed |
| AS31543 | myNet GmbH | not declared | Observed |
| AS12637 | SEEWEB s.r.l. | not declared | Observed |
| AS13030 | Init7 (Switzerland) Ltd. | 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 AS20912 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 |
|---|---|---|---|---|---|
| 193.36.108.0/23 | RIPE | — | MNT-IT-WINGSOFT-1 | 2021-06-23 | Not announced |
| 193.36.108.0/24 | RIPE | — | MNT-IT-WINGSOFT-1 | 2021-06-30 | Not announced |
| 193.36.109.0/24 | RIPE | — | MNT-IT-WINGSOFT-1 | 2021-06-30 | Not announced |
| 193.36.110.0/24 | RIPE | — | MNT-IT-WINGSOFT-1 | 2025-08-11 | Not announced |
| 193.36.111.0/24 | RIPE | — | MNT-IT-WINGSOFT-1 | 2025-08-11 | Not announced |
| 212.66.96.0/20 | RIPE | PANSERVICE network block | PANSERVICE-NOC | 2010-02-19 | Not announced |
| 212.66.112.0/20 | RIPE | PANSERVICE network block | PANSERVICE-NOC | 2010-02-19 | Not announced |
| 212.66.118.0/23 | RIPE | PANSERVICE more specific network block | PANSERVICE-NOC | 2017-02-15 | Not announced |
| 46.102.96.0/22 | RADB | — | MAINT-PL-SCM | 2025-03-04 | Announced |
| 46.102.96.0/22 | RIPE | — | PL-SCM-1-MNT | 2025-03-04 | Announced |
| 77.39.192.0/20 | RIPE | PANSERVICE network block | PANSERVICE-NOC | 2017-09-20 | Announced |
| 77.39.216.0/22 | RIPE | PANSERVICE network block | PANSERVICE-NOC | 2017-09-20 | Announced |
| 85.119.176.0/21 | RIPE | PANSERVICE network block | PANSERVICE-NOC | 2014-08-01 | Announced |
| 185.109.188.0/22 | RIPE | PANSERVICE network block | PANSERVICE-NOC | 2015-07-17 | Announced |
| 193.36.108.0/22 | RIPE | — | MNT-IT-WINGSOFT-1 | 2025-07-18 | Announced |
| 212.66.96.0/19 | RIPE | PANSERVICE network block | PANSERVICE-NOC | 2010-02-19 | Announced |
| 212.66.120.0/22 | RIPE | PANSERVICE more specific network block | PANSERVICE-NOC | 2017-03-20 | Announced |
| 2001:40d0::/32 | RIPE | PANSERVICE | PANSERVICE-NOC | 2005-04-19 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS20912 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-PANSERVICE | PeeringDB | Declared by the operator as its own set |
AS-HURRICANEV6 | RADB | Lists AS20912 as a direct member |
AS-PANSERVICE | RIPE | Lists AS20912 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS20912 as a direct member |
AS-RETN-ACTUAL-V6 | RIPE | Lists AS20912 as a direct member |
AS-RIS-RRC10 | RIPE | Lists AS20912 as a direct member |
AS-SEFLOW | RIPE | Lists AS20912 as a direct member |
AS-SEFLOW6 | RIPE | Lists AS20912 as a direct member |
AS12637:AS-CUSTOMERS-V6 | RIPE | Lists AS20912 as a direct member |
AS15589:AS-NAMEX-PEERS | RIPE | Lists AS20912 as a direct member |
AS3303:AS-SWCMPEERS | RIPE | Lists AS20912 as a direct member |
RPKI from rpki-client, validated 2026-10-11 12:23 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-11. Cross-check on bgp.he.net.