Routing security
AS208022 TNEX Mehmet Ali Kilic
Unclassified RIPE
RPKI valid
100%
61 of 61 announcements
RPKI invalid
0
none
No ROA
0
not covered by any ROA
IRR registered
100%
0 missing · 0 other origin
ROAs
49
authorising this AS
Announcements
What this network originates
Every prefix observed with AS208022 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a0a:282::/32 | RPKI valid | IRR | 29 |
| 2a0a:283::/32 | RPKI valid | IRR | 29 |
| 2a0a:284::/32 | RPKI valid | IRR | 29 |
| 2a0a:285::/32 | RPKI valid | IRR | 29 |
| 2a0a:286::/32 | RPKI valid | IRR | 29 |
| 2a05:88c0::/32 | RPKI valid | IRR | 29 |
| 2a05:88c1::/32 | RPKI valid | IRR | 29 |
| 2a05:88c2::/32 | RPKI valid | IRR | 29 |
| 2a05:88c3::/32 | RPKI valid | IRR | 29 |
| 2a05:88c4::/32 | RPKI valid | IRR | 29 |
| 2a05:88c5::/32 | RPKI valid | IRR | 29 |
| 2a05:88c6::/32 | RPKI valid | IRR | 29 |
| 2a05:88c7::/32 | RPKI valid | IRR | 29 |
| 2a10:7f40::/32 | RPKI valid | IRR | 29 |
| 2a10:7f41::/32 | RPKI valid | IRR | 29 |
| 2a10:7f42::/32 | RPKI valid | IRR | 29 |
| 2a10:7f43::/32 | RPKI valid | IRR | 29 |
| 2a10:7f44::/32 | RPKI valid | IRR | 29 |
| 2a10:7f45::/32 | RPKI valid | IRR | 29 |
| 2a10:7f46::/32 | RPKI valid | IRR | 29 |
| 2a10:7f47::/32 | RPKI valid | IRR | 29 |
| 2a10:7fc0::/32 | RPKI valid | IRR | 29 |
| 2a10:7fc1::/32 | RPKI valid | IRR | 29 |
| 2a10:7fc2::/32 | RPKI valid | IRR | 29 |
| 2a10:7fc3::/32 | RPKI valid | IRR | 29 |
| 2a10:7fc4::/32 | RPKI valid | IRR | 29 |
| 2a10:7fc5::/32 | RPKI valid | IRR | 29 |
| 2a10:7fc6::/32 | RPKI valid | IRR | 29 |
| 2a10:7fc7::/32 | RPKI valid | IRR | 29 |
| 2a10:3300::/32 | RPKI valid | IRR | 29 |
| 2a10:3301::/32 | RPKI valid | IRR | 29 |
| 2a10:3302::/32 | RPKI valid | IRR | 29 |
| 2a10:3303::/32 | RPKI valid | IRR | 29 |
| 2a10:3304::/32 | RPKI valid | IRR | 29 |
| 2a10:3305::/32 | RPKI valid | IRR | 29 |
| 2a10:3306::/32 | RPKI valid | IRR | 29 |
| 2a10:3307::/32 | RPKI valid | IRR | 29 |
| 2a11:3785::/32 | RPKI valid | IRR | 29 |
| 2a11:d100::/32 | RPKI valid | IRR | 29 |
| 2a11:d101::/32 | RPKI valid | IRR | 29 |
| 2a11:d102::/32 | RPKI valid | IRR | 29 |
| 2a11:d103::/32 | RPKI valid | IRR | 29 |
| 2a11:d104::/32 | RPKI valid | IRR | 29 |
| 2a11:d105::/32 | RPKI valid | IRR | 29 |
| 2a11:d106::/32 | RPKI valid | IRR | 29 |
| 2a11:d107::/32 | RPKI valid | IRR | 29 |
| 2a12:ef40::/32 | RPKI valid | IRR | 29 |
| 2a12:ef42::/32 | RPKI valid | IRR | 29 |
| 2a12:ef43::/32 | RPKI valid | IRR | 29 |
| 2a12:ef44::/32 | RPKI valid | IRR | 29 |
| 2a12:ef45::/32 | RPKI valid | IRR | 29 |
| 2a12:ef46::/32 | RPKI valid | IRR | 29 |
| 2a12:ef47::/32 | RPKI valid | IRR | 29 |
| 2a13:63c0::/32 | RPKI valid | IRR | 29 |
| 2a13:63c1::/32 | RPKI valid | IRR | 29 |
| 2a13:63c2::/32 | RPKI valid | IRR | 29 |
| 2a13:63c3::/32 | RPKI valid | IRR | 29 |
| 2a13:63c4::/32 | RPKI valid | IRR | 29 |
| 2a13:63c5::/32 | RPKI valid | IRR | 29 |
| 2a13:63c6::/32 | RPKI valid | IRR | 29 |
| 2a13:63c7::/32 | RPKI valid | IRR | 29 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS208022 may originate these prefixes, up to the maximum length shown.
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.
IRR
Registered route objects
Route objects naming AS208022 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 |
|---|---|---|---|---|---|
| 2a05:88c0::/29 | RADB | Vultr Customer Route | MAINT-AS20473 | 2025-12-12 | Not announced |
| 2a0a:281::/32 | RADB | Vultr Customer Route | MAINT-AS20473 | 2023-11-13 | Not announced |
| 2a0a:281::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2023-03-30 | Not announced |
| 2a10:3300::/29 | RADB | Vultr Customer Route | MAINT-AS20473 | 2025-12-12 | Not announced |
| 2a10:7f40::/29 | RADB | Vultr Customer Route | MAINT-AS20473 | 2025-12-12 | Not announced |
| 2a10:7fc0::/29 | RADB | Vultr Customer Route | MAINT-AS20473 | 2025-12-12 | Not announced |
| 2a11:3780::/29 | RIPE | Pool Network | LIR-TR-MEHMET5-1-MNT | 2023-08-28 | Not announced |
| 2a11:3780::/32 | RADB | Vultr Customer Route | MAINT-AS20473 | 2023-11-14 | Not announced |
| 2a11:3780::/32 | RIPE | Brazil IPv6 Network | LIR-TR-MEHMET5-1-MNT | 2023-08-17 | Not announced |
| 2a11:3781::/32 | RADB | Vultr Customer Route | MAINT-AS20473 | 2023-11-14 | Not announced |
| 2a11:3781::/32 | RIPE | India IPv6 Network | LIR-TR-MEHMET5-1-MNT | 2023-08-17 | Not announced |
| 2a11:3782::/32 | RADB | Vultr Customer Route | MAINT-AS20473 | 2023-11-14 | Not announced |
| 2a11:3782::/32 | RIPE | Indonesia IPv6 Network | LIR-TR-MEHMET5-1-MNT | 2023-08-17 | Not announced |
| 2a11:3783::/32 | RADB | Vultr Customer Route | MAINT-AS20473 | 2023-11-14 | Not announced |
| 2a11:3783::/32 | RIPE | Mexico IPv6 Network | LIR-TR-MEHMET5-1-MNT | 2023-08-17 | Not announced |
| 2a11:3784::/32 | RADB | Vultr Customer Route | MAINT-AS20473 | 2023-11-14 | Not announced |
| 2a11:3784::/32 | RIPE | Colombia IPv6 Network | LIR-TR-MEHMET5-1-MNT | 2023-08-17 | Not announced |
| 2a11:3786::/32 | RADB | Vultr Customer Route | MAINT-AS20473 | 2023-11-14 | Not announced |
| 2a11:3786::/32 | RIPE | Argentina IPv6 Network | LIR-TR-MEHMET5-1-MNT | 2023-08-17 | Not announced |
| 2a11:3787::/32 | RADB | Vultr Customer Route | MAINT-AS20473 | 2023-11-14 | Not announced |
| 2a11:3787::/32 | RIPE | Pakistan IPv6 Network | LIR-TR-MEHMET5-1-MNT | 2023-08-17 | Not announced |
| 2a11:d100::/29 | RADB | Vultr Customer Route | MAINT-AS20473 | 2025-12-12 | Not announced |
| 2a12:ef40::/29 | RIPE | Pool Network | LIR-TR-MEHMET5-1-MNT | 2023-02-09 | Not announced |
| 2a12:ef41::/32 | RIPE | India IPv6 Network | LIR-TR-MEHMET5-1-MNT | 2023-02-09 | Not announced |
| 2a13:63c0::/29 | RADB | Vultr Customer Route | MAINT-AS20473 | 2025-12-12 | Not announced |
| 2a05:88c0::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a05:88c1::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a05:88c2::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a05:88c3::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a05:88c4::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a05:88c5::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a05:88c6::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a05:88c7::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a0a:282::/32 | RADB | Vultr Customer Route | MAINT-AS20473 | 2023-11-14 | Announced |
| 2a0a:282::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2023-08-08 | Announced |
| 2a0a:283::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2024-11-18 | Announced |
| 2a0a:284::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2024-11-18 | Announced |
| 2a0a:285::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2024-11-18 | Announced |
| 2a0a:286::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2024-11-18 | Announced |
| 2a10:3300::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:3301::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:3302::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:3303::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:3304::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:3305::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:3306::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:3307::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:7f40::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:7f41::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:7f42::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:7f43::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:7f44::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:7f45::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:7f46::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:7f47::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:7fc0::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:7fc1::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:7fc2::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:7fc3::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:7fc4::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:7fc5::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:7fc6::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a10:7fc7::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a11:3785::/32 | RADB | Vultr Customer Route | MAINT-AS20473 | 2023-11-14 | Announced |
| 2a11:3785::/32 | RIPE | Turkey IPv6 Network | LIR-TR-MEHMET5-1-MNT | 2023-08-17 | Announced |
| 2a11:d100::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a11:d101::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a11:d102::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a11:d103::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a11:d104::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a11:d105::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a11:d106::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a11:d107::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-11 | Announced |
| 2a12:ef40::/32 | RADB | Vultr Customer Route | MAINT-AS20473 | 2026-09-26 | Announced |
| 2a12:ef40::/32 | RIPE | Brazil IPv6 Network | LIR-TR-MEHMET5-1-MNT | 2023-02-09 | Announced |
| 2a12:ef42::/32 | RIPE | Indonesia IPv6 Network | LIR-TR-MEHMET5-1-MNT | 2023-02-09 | Announced |
| 2a12:ef43::/32 | RIPE | Mexico IPv6 Network | LIR-TR-MEHMET5-1-MNT | 2023-02-09 | Announced |
| 2a12:ef44::/32 | RIPE | Colombia IPv6 Network | LIR-TR-MEHMET5-1-MNT | 2023-02-09 | Announced |
| 2a12:ef45::/32 | RIPE | Turkey IPv6 Network | LIR-TR-MEHMET5-1-MNT | 2023-02-09 | Announced |
| 2a12:ef46::/32 | RIPE | Argentina IPv6 Network | LIR-TR-MEHMET5-1-MNT | 2023-02-09 | Announced |
| 2a12:ef47::/32 | RIPE | Pakistan IPv6 Network | LIR-TR-MEHMET5-1-MNT | 2023-02-09 | Announced |
| 2a13:63c0::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-12 | Announced |
| 2a13:63c1::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-12 | Announced |
| 2a13:63c2::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-12 | Announced |
| 2a13:63c3::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-12 | Announced |
| 2a13:63c4::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-12 | Announced |
| 2a13:63c5::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-12 | Announced |
| 2a13:63c6::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-12 | Announced |
| 2a13:63c7::/32 | RIPE | — | LIR-TR-MEHMET5-1-MNT | 2025-12-12 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS208022 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS208022:AS-MEHMET | PeeringDB | Declared by the operator as its own set |
AS-E1-AUTOMATION-CUSTOMER | RADB | Lists AS208022 as a direct member |
AS20473:AS-VULTR | RADB | Lists AS208022 as a direct member |
AS208022:AS-MEHMET | RIPE | Lists AS208022 as a direct member |
RPKI from rpki-client, validated 2026-11-06 13:02 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-11-06. Cross-check on bgp.he.net.