Routing security
AS48606 SYSTEM36 LLC
Hosting RIPE Network Services
Announcements
What this network originates
Every prefix observed with AS48606 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a0c:5705:1000::/36 | RPKI valid | IRR | 29 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS48606 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 2a0c:5705::/32 | /48 | RIPENCC |
| 2a0c:5705:1000::/36 | /36 | 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 |
|---|---|---|---|
| AS30893 | No ACK Group Holding AB | Declared | not observed |
| AS54681 | Aubrey Rose | Declared | not observed |
| AS57974 | unnamed | Declared | not observed |
| AS59678 | SYSTEM36 LLC | Declared | Observed |
| AS210691 | unnamed | Declared | not observed |
| AS212276 | unnamed | 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 AS48606 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 |
|---|---|---|---|---|---|
| 2a0c:5705::/32 | RIPE | — | MNT-NOACKHOSTING | 2023-03-28 | Not announced |
| 2a0c:5705:2000::/36 | RIPE | — | ROUTE36-MNT | 2023-04-07 | Not announced |
| 2a0c:5705:3000::/36 | RIPE | — | ROUTE36-MNT | 2023-04-11 | Not announced |
| 2a0c:5705:4000::/36 | RIPE | — | ROUTE36-MNT | 2023-06-22 | Not announced |
| 2a0c:5705:5000::/36 | RIPE | — | ROUTE36-MNT | 2023-06-22 | Not announced |
| 2a0c:5705:6000::/36 | RIPE | — | ROUTE36-MNT | 2023-06-22 | Not announced |
| 2a0c:5705:7000::/36 | RIPE | — | ROUTE36-MNT | 2023-06-22 | Not announced |
| 2a0c:5705:8000::/36 | RADB | Path Network, Inc. - Anycasted Proxy-Route for AS48606 | MAINT-AS396998 | 2023-11-13 | Not announced |
| 2a0c:5705:8000::/36 | RIPE | — | ROUTE36-MNT | 2023-06-22 | Not announced |
| 2a0c:5705:9000::/36 | RIPE | — | ROUTE36-MNT | 2023-06-23 | Not announced |
| 2a0c:5705:1000::/36 | RIPE | — | ROUTE36-MNT | 2023-04-07 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS48606 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS48606:AS-ROUTE36 | PeeringDB | Declared by the operator as its own set |
AS-IPARTNERS | RIPE | Lists AS48606 as a direct member |
AS30893:AS-NOACKCUST | RIPE | Lists AS48606 as a direct member |
AS48606:AS-ROUTE36 | RIPE | Lists AS48606 as a direct member |
AS5617:AS-AMICA | RIPE | Lists AS48606 as a direct member |
AS57974:AS-CUSTOMERS | RIPE | Lists AS48606 as a direct member |
AS59678:AS-SYS36 | RIPE | Lists AS48606 as a direct member |
AS8246:AS-TPNET | RIPE | Lists AS48606 as a direct member |
RPKI from rpki-client, validated 2026-11-13 13:05 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-11-13. Cross-check on bgp.he.net.