AS56582 NETFACTOR-ASN Netfactor Telekominikasyon ve Teknoloji Hizmetleri San. ve Tic. A.S.
🇹🇷Org handle: ORG-NTVT1-RIPE
Netfactor - ISP / Broadband services (TR)
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
50total
49 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)15,648
Announced (BGP)12,544
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Routing hygiene
Score 26/100 · Medium riskRPKI ROA coverage
92.3%
3 prefixes RPKI invalid
IRR route objects
88.5%
5 prefixes registered for another origin
Hijack signals
1
0 announced against others' ROAs, 1 own announced by others
Upstreams
2
diversity 14/100
- Routes concentrated on one upstream (92% of routes)
- 2 prefixes registered in IRR route objects for another active network and not authorized by a ROA
- 8% of announced prefixes (4 of 52) have no valid ROA, 3 of them RPKI invalid
Based on 52 announced prefixes, updated daily (2026-10-21). How the score works · RPKI explained
Announced Prefixes
(BGP)50|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | - | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
1-10 of 50
1 / 5
Allocated Prefixes
(RIR)44Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.169.64.0/22 | 🇹🇷 TR | RIPENCC | allocated |
| 31.169.69.0/24 | 🇹🇷 TR | RIPENCC | allocated |
| 31.169.70.0/23 | 🇹🇷 TR | RIPENCC | allocated |
| 31.169.72.0/24 | 🇹🇷 TR | RIPENCC | allocated |
| 31.169.74.0/23 | 🇹🇷 TR | RIPENCC | allocated |
| 31.169.74.0/24 | 🇹🇷 TR | RIPE | assigned |
| 31.169.76.0/22 | 🇹🇷 TR | RIPENCC | allocated |
| 31.169.77.0/24 | 🇹🇷 TR | RIPE | assigned |
| 31.169.80.0/21 | 🇹🇷 TR | RIPENCC | allocated |
| 31.169.82.0/24 | 🇹🇷 TR | RIPE | assigned |
1-10 of 44
1 / 5
All 50 announced prefixes of AS56582 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS56582 hands its own prefixes to: transit providers, or peers at an exchange.
Abuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- How to run an ASPA checkVerify the upstream providers listed above
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/56582Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/56582" | jq