Network report
Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Warning: AS47524 (AS-TURKSAT) announces 801 IPv4 and 185 IPv6 prefixes. 2 warnings
| AS page | AS47524 |
|---|---|
| Holder | AS-TURKSAT Turksat Uydu Haberlesme Kablo TV ve Isletme A.S. |
| Allocation | RIPE NCC, Turkey (TR), allocated 2008-07-02 |
| Prefixes (IPv4 / IPv6) | 801 / 185 |
| RPKI valid | 100% (986 / 986) |
| Upstreams and peers | 14 |
| Peering policy | Open |
What to fix
-
Warning
176 of 986 announced prefixes have no IRR route object: 2a00:1d58:5000::/38, 2a00:1d58:b200::/39, 2a00:1d58:f01e::/48, 2a00:1d58:f806::/48, 2a00:1d58:f812::/48 (+171).
Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.
Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS47524 in your RIR’s IRR database (or RADB).
route6: 2a00:1d58:5000::/38 origin: AS47524 route6: 2a00:1d58:b200::/39 origin: AS47524 route6: 2a00:1d58:f01e::/48 origin: AS47524
-
Warning
No public NOC, policy or technical contact.
Other networks use these addresses to set up peering and to reach you during an incident.
Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.
Checks
Routing and RPKI 176 of 986 announced prefixes have no IRR route object: 2a00:1d58:5000::/38, 2a00:1d58:b200::/39, 2a00:1d58:f01e::/48, 2a00:1d58:f806::/48, 2a00:1d58:f812::/48 (+171).
- Pass: AS47524 announces 801 IPv4 and 185 IPv6 prefixes.
- Pass: All 986 announced prefixes are RPKI valid.
- Warning: 176 of 986 announced prefixes have no IRR route object: 2a00:1d58:5000::/38, 2a00:1d58:b200::/39, 2a00:1d58:f01e::/48, 2a00:1d58:f806::/48, 2a00:1d58:f812::/48 (+171).
- Info: 14 upstreams and peers, 3 downstream networks seen.
| Holder | AS-TURKSAT Turksat Uydu Haberlesme Kablo TV ve Isletme A.S. |
|---|---|
| IPv4 prefixes | 801 |
| IPv6 prefixes | 185 |
| RPKI | 986 valid |
| Without IRR route object | 176 |
| Downstream networks | 3 |
Upstreams and peers seen to the left 14
Announced prefixes 986
Showing the first 100.
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.db.ripe.net.
- Pass: Found at rdap.db.ripe.net.
| Name | AS-TURKSAT |
|---|---|
| Handle | AS47524 |
| Range | AS47524 |
| Status | active |
| Registered | 2008-07-02T09:04:56Z |
| Last changed | 2026-04-30T11:38:36Z |
| Abuse contact | abuse@turksat.com.tr |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | Turkey (TR) |
| Delegated on | 2008-07-02 |
| Status | Allocated |
| Delegated range | AS47524 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | MNT-AS47524 | |
| registrant | Turksat Uydu Haberlesme Kablo TV ve Isletme A.S. | |
| registrant | RIPE-NCC-END-MNT | |
| abuse | Abuse Mailbox | abuse@turksat.com.tr |
Source: https://rdap.db.ripe.net/autnum/47524. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.
Open in WHOIS / RDAP lookupPeeringDB No public NOC, policy or technical contact.
- Pass: AS47524 is in PeeringDB as TURKSAT.
- Info: Peering policy: Open.
- Info: Present at 2 internet exchanges with 2 ports (200G in total).
- Warning: No public NOC, policy or technical contact.
| Network | TURKSAT |
|---|---|
| AS number | AS47524 |
| Type | Cable/DSL/ISP, Middle East |
| Website | https://www.turksat.com.tr/ |
| IRR as-set | AS47524:AS-TURKSAT |
| Prefixes (IPv4 / IPv6) | 1000 / 1000 |
| Traffic | 1-5Tbps, Heavy Inbound |
| Peering policy | Open |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2026-03-31 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup