Routing security
AS48326 DATANETWORKS
Residential RIPE
Announcements
What this network originates
Every prefix observed with AS48326 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a00:b000::/32 | RPKI valid | IRR | 33 |
| 2a00:b000::/48 | RPKI valid | IRR | 34 |
| 2a00:b000:1::/48 | RPKI valid | IRR | 33 |
| 2a00:b000:2::/48 | RPKI valid | IRR | 34 |
| 46.228.208.0/20 | RPKI valid | IRR | 52 |
| 46.228.208.0/21 | RPKI valid | IRR covering | 17 |
| 46.228.216.0/21 | RPKI valid | IRR covering | 17 |
| 46.228.221.0/24 | RPKI valid | IRR | 20 |
| 46.228.223.0/24 | RPKI valid | IRR | 20 |
| 94.229.32.0/20 | RPKI valid | IRR | 52 |
| 94.229.32.0/21 | RPKI valid | IRR | 17 |
| 94.229.40.0/21 | RPKI valid | IRR | 17 |
| 193.8.84.0/23 | RPKI valid | IRR | 52 |
| 193.8.84.0/24 | RPKI valid | IRR | 16 |
| 193.8.85.0/24 | RPKI valid | IRR | 16 |
| 193.8.92.0/23 | RPKI valid | IRR | 52 |
| 193.8.92.0/24 | RPKI valid | IRR covering | 16 |
| 193.8.93.0/24 | RPKI valid | IRR | 16 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS48326 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 46.228.208.0/20 | /20 | RIPENCC |
| 46.228.208.0/21 | /21 | RIPENCC |
| 46.228.216.0/21 | /21 | RIPENCC |
| 46.228.221.0/24 | /27 | RIPENCC |
| 46.228.223.0/24 | /27 | RIPENCC |
| 94.229.32.0/20 | /20 | RIPENCC |
| 94.229.32.0/21 | /21 | RIPENCC |
| 94.229.40.0/21 | /21 | RIPENCC |
| 193.8.84.0/23 | /23 | RIPENCC |
| 193.8.84.0/24 | /24 | RIPENCC |
| 193.8.85.0/24 | /24 | RIPENCC |
| 193.8.92.0/23 | /23 | RIPENCC |
| 193.8.92.0/24 | /24 | RIPENCC |
| 193.8.93.0/24 | /24 | RIPENCC |
| 2a00:b000::/32 | /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 |
|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Declared | Observed |
| AS31117 | ENERGOTEL a.s. | Declared | not observed |
| AS39392 | SH.cz s.r.o. | Declared | Observed |
| AS60068 | Datacamp Limited | Declared | Observed |
| AS3303 | Swisscom (Schweiz) AG | not declared | Observed |
| AS31230 | Slovak University of Technology in Bratislava | not declared | Observed |
| AS33891 | Core-Backbone GmbH | not declared | Observed |
| AS24482 | SG.GS | not declared | Observed |
| AS29504 | Freenet Liberec, z.s. | not declared | Observed |
| AS20562 | Broadband Hosting B.V. | not declared | Observed |
| AS37721 | Virtual Technologies & Solutions | not declared | Observed |
| AS44066 | firstcolo 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 AS48326 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 |
|---|---|---|---|---|---|
| 46.228.222.0/24 | RIPE | FOST | CDSL-MNT | 2017-02-14 | Not announced |
| 194.145.206.0/23 | RIPE | ALTERNET-BACKBONE-1 | ALTERNETSK-MNT | 2011-12-06 | Not announced |
| 46.228.208.0/20 | RIPE | DataNetworks | CDSL-MNT | 2011-07-28 | Announced |
| 46.228.221.0/24 | RIPE | — | CDSL-MNT | 2026-04-17 | Announced |
| 46.228.223.0/24 | RIPE | — | CDSL-MNT | 2017-10-25 | Announced |
| 94.229.32.0/20 | RIPE | DataNetworks | CDSL-MNT | 2011-01-31 | Announced |
| 94.229.32.0/21 | RIPE | DataNetworks | CDSL-MNT | 2016-11-17 | Announced |
| 94.229.40.0/21 | RIPE | DataNetworks | CDSL-MNT | 2016-11-17 | Announced |
| 193.8.84.0/23 | RIPE | — | CDSL-MNT | 2019-10-04 | Announced |
| 193.8.84.0/24 | RIPE | — | CDSL-MNT | 2019-10-04 | Announced |
| 193.8.85.0/24 | RIPE | — | CDSL-MNT | 2019-10-04 | Announced |
| 193.8.92.0/23 | RIPE | — | CDSL-MNT | 2019-10-04 | Announced |
| 193.8.93.0/24 | RIPE | — | CDSL-MNT | 2019-10-04 | Announced |
| 2a00:b000::/32 | RIPE | — | CDSL-MNT | 2023-02-22 | Announced |
| 2a00:b000::/48 | RIPE | — | MARKY-MNT | 2023-02-22 | Announced |
| 2a00:b000:1::/48 | RIPE | — | MARKY-MNT | 2025-01-14 | Announced |
| 2a00:b000:2::/48 | RIPE | — | MARKY-MNT | 2025-01-14 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS48326 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-DATANETWORKS | RIPE | Lists AS48326 as a direct member |
AS-EMAXSIXPEERS | RIPE | Lists AS48326 as a direct member |
AS-ENERGOTEL | RIPE | Lists AS48326 as a direct member |
AS-ENERGOTEL_SIX_PEERS | RIPE | Lists AS48326 as a direct member |
AS-HURRICANEV6 | RADB | Lists AS48326 as a direct member |
AS-KAORA | RIPE | Lists AS48326 as a direct member |
AS-RADIOLAN | RIPE | Lists AS48326 as a direct member |
AS-SIXSK-MEMBERS | RIPE | Lists AS48326 as a direct member |
AS-SIXSTIP-SET | RIPE | Lists AS48326 as a direct member |
AS-SLOVANET | RIPE | Lists AS48326 as a direct member |
AS42000:AS-SIXSK-PEERINGS | RIPE | Lists AS48326 as a direct member |
AS5578:AS-SIXPEERS | RIPE | Lists AS48326 as a direct member |
RPKI from rpki-client, validated 2026-10-16 12:09 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-16. Cross-check on bgp.he.net.