Routing security
AS30764 PODA-AS
Residential ARIN
Announcements
What this network originates
Every prefix observed with AS30764 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a00:ca8::/29 | RPKI valid | IRR | 29 |
| 2a02:c38::/32 | RPKI valid | IRR | 31 |
| 46.47.128.0/18 | RPKI valid | IRR | 53 |
| 62.129.32.0/19 | RPKI valid | IRR | 53 |
| 78.157.128.0/19 | RPKI valid | IRR | 53 |
| 82.209.0.0/18 | RPKI valid | IRR | 53 |
| 85.135.0.0/17 | RPKI valid | IRR | 53 |
| 89.29.0.0/17 | RPKI valid | IRR | 53 |
| 94.242.64.0/18 | RPKI valid | IRR | 53 |
| 128.0.176.0/20 | RPKI valid | IRR | 53 |
| 164.215.112.0/20 | RPKI valid | IRR | 53 |
| 185.5.68.0/22 | RPKI valid | IRR | 53 |
| 193.165.0.0/16 | RPKI valid | IRR | 53 |
| 193.165.0.0/24 | RPKI valid | IRR covering | 53 |
| 193.165.96.0/23 | RPKI valid | IRR covering | 53 |
| 193.165.236.0/23 | RPKI valid | IRR covering | 53 |
| 212.109.176.0/20 | RPKI valid | IRR | 53 |
| 213.216.32.0/19 | RPKI valid | IRR | 53 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS30764 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 46.47.128.0/18 | /18 | RIPENCC |
| 62.129.32.0/19 | /19 | RIPENCC |
| 78.157.128.0/19 | /19 | RIPENCC |
| 82.209.0.0/18 | /18 | RIPENCC |
| 85.135.0.0/17 | /17 | RIPENCC |
| 89.29.0.0/17 | /17 | RIPENCC |
| 94.242.64.0/18 | /18 | RIPENCC |
| 128.0.176.0/20 | /20 | RIPENCC |
| 164.215.112.0/20 | /20 | RIPENCC |
| 185.5.68.0/22 | /22 | RIPENCC |
| 193.165.0.0/16 | /16 | RIPENCC |
| 193.165.0.0/24 | /24 | RIPENCC |
| 193.165.57.0/24 | /24 | RIPENCC |
| 193.165.58.0/23 | /23 | RIPENCC |
| 193.165.61.0/24 | /24 | RIPENCC |
| 193.165.96.0/23 | /23 | RIPENCC |
| 193.165.236.0/23 | /23 | RIPENCC |
| 212.109.176.0/20 | /20 | RIPENCC |
| 213.216.32.0/19 | /19 | RIPENCC |
| 2a00:ca8::/29 | /29 | RIPENCC |
| 2a00:ca8::/32 | /32 | RIPENCC |
| 2a02:c38::/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 |
| AS1299 | Arelion Sweden AB | Declared | Observed |
| AS39392 | SH.cz s.r.o. | Declared | Observed |
| AS6939 | Hurricane Electric LLC | not declared | Observed |
| AS24482 | SG.GS | not declared | Observed |
| AS29504 | Freenet Liberec, z.s. | not declared | Observed |
| AS37721 | Virtual Technologies & Solutions | not declared | Observed |
| AS47232 | ISP Alliance a.s. | not declared | Observed |
| AS1764 | Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH | not declared | Observed |
| AS6461 | Zayo Bandwidth | not declared | Observed |
| AS20562 | Broadband Hosting B.V. | 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 AS30764 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 |
|---|---|---|---|---|---|
| 2a00:ca8::/32 | RIPE | PODA a.s. | PODACZ-MNT | 2010-06-11 | Not announced |
| 46.47.128.0/18 | RIPE | PODA-NET | PODACZ-MNT | 2010-11-05 | Announced |
| 62.129.32.0/19 | RIPE | PODA-NET | PODACZ-MNT | 2003-11-28 | Announced |
| 78.157.128.0/19 | RIPE | PODA-NET | PODACZ-MNT | 2010-06-07 | Announced |
| 82.209.0.0/18 | RIPE | PODA-NET | PODACZ-MNT | 2003-11-28 | Announced |
| 85.135.0.0/17 | RIPE | PODA-NET | PODACZ-MNT | 2004-12-16 | Announced |
| 89.29.0.0/17 | RIPE | PODA-NET | PODACZ-MNT | 2006-11-30 | Announced |
| 94.242.64.0/18 | RIPE | PODA-NET | PODACZ-MNT | 2008-10-18 | Announced |
| 128.0.176.0/20 | RIPE | PODA-NET | PODACZ-MNT | 2012-09-17 | Announced |
| 164.215.112.0/20 | RIPE | PODA-NET | PODACZ-MNT | 2011-11-25 | Announced |
| 185.5.68.0/22 | RIPE | PODA-NET | PODACZ-MNT | 2021-02-10 | Announced |
| 193.165.0.0/16 | RIPE | PODA a.s. IPv4 | MNT-SKYNET | 2017-08-22 | Announced |
| 212.109.176.0/20 | RIPE | PODA-NET | PODACZ-MNT | 2012-03-05 | Announced |
| 213.216.32.0/19 | RIPE | PODA a.s. IPv4 | MNT-SKYNET | 2017-08-22 | Announced |
| 2a00:ca8::/29 | RIPE | — | PODACZ-MNT | 2026-08-10 | Announced |
| 2a02:c38::/32 | RIPE | PODA a.s. IPv6 | MNT-SKYNET | 2017-08-22 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS30764 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-PODACZ | RIPE | Lists AS30764 as a direct member |
AS-TO2-NIX-PEER | RIPE | Lists AS30764 as a direct member |
AS12570:AS-NIX-PEERS | RIPE | Lists AS30764 as a direct member |
AS174:AS-COGC-034 | RADB | Lists AS30764 as a direct member |
AS42000:AS-NIXCZ-PEERINGS | RIPE | Lists AS30764 as a direct member |
AS8251:AS-NIX-PEERINGS | RIPE | Lists AS30764 as a direct member |
RPKI from rpki-client, validated 2026-10-15 12:09 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-15. Cross-check on bgp.he.net.