Routing security
AS8396 TEE-
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS8396 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 212.70.192.0/19 | RPKI valid | IRR | 57 |
| 212.70.204.0/24 | RPKI valid | IRR | 52 |
| 212.70.206.0/24 | RPKI valid | IRR covering | 53 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS8396 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 212.70.192.0/19 | /19 | RIPENCC |
| 212.70.204.0/24 | /24 | RIPENCC |
| 212.70.206.0/24 | /24 | 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 |
|---|---|---|---|
| AS56910 | Digital Realty Hellas Single Member S.A | Declared | not observed |
| AS199081 | Lancom Ltd. | Declared | Observed |
| AS213835 | Solidity Technology Services SA | 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 AS8396 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 |
|---|---|---|---|---|---|
| 212.70.192.0/19 | RIPE | Technical Chamber of Greece | TEE-MNT | 2003-06-11 | Announced |
| 212.70.204.0/24 | RIPE | — | TEE-MNT | 2024-03-14 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS8396 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-DRT | RIPE | Lists AS8396 as a direct member |
AS-FORTHNET-LAMDAHELLIX | RIPE | Lists AS8396 as a direct member |
AS-HURRICANE | RADB | Lists AS8396 as a direct member |
AS-LANCOM-GR | RIPE | Lists AS8396 as a direct member |
AS-OTEGLOBE | RIPE | Lists AS8396 as a direct member |
AS-OTENET-TEST | RIPE | Lists AS8396 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS8396 as a direct member |
AS-TRANSROUTE-SPEC | RIPE | Lists AS8396 as a direct member |
AS-WIND-HELLAS | RIPE | Lists AS8396 as a direct member |
AS213835:AS-CUSTOMERS | RIPE | Lists AS8396 as a direct member |
AS3329:AS-HOLTR | RIPE | Lists AS8396 as a direct member |
AS3491:AS-CUSTOMERS-EU | RADB | Lists AS8396 as a direct member |
AS56910:AS-CUSTOMERS | RIPE | Lists AS8396 as a direct member |
AS56910:AS-TO-AIX | RIPE | Lists AS8396 as a direct member |
RPKI from rpki-client, validated 2026-10-13 12:16 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-13. Cross-check on bgp.he.net.