{"tool":"network-report","status":"warn","input":{"query":"AS42083"},"findings":[{"level":"warn","text":"AS42083 (GUNEYDOGUTELEKOM) announces 10 IPv4 and 0 IPv6 prefixes.","title":"AS42083 (GUNEYDOGUTELEKOM) announces 10 IPv4 and 0 IPv6 prefixes.","params":{"query":"AS42083","who":"AS42083 (GUNEYDOGUTELEKOM)","v4":10,"v6":0}},{"level":"warn","text":"No IPv6 prefixes announced.","title":"No IPv6 prefixes announced.","params":{},"detail":"Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.","fix":"Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it."},{"level":"warn","text":"No IRR as-set is listed.","title":"No IRR as-set is listed.","params":{},"detail":"Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.","fix":"Create an as-set in your RIR’s IRR database and add it to your PeeringDB record."}],"data":{"query":"AS42083","kind":"asn","special":null,"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"TR","country":"Turkey","date":"2017-06-16","status":"allocated","range":"AS42083","opaque_id":"fa139869-f469-4be0-ad0d-c2533bf03c7e","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS42083","who":"AS42083 (GUNEYDOGUTELEKOM)","v4":10,"v6":0}},"seconds":1.8,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":42083,"v4":10,"v6":0}},{"level":"warn","title":"No IPv6 prefixes announced.","params":[],"detail":"Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.","fix":"Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it."},{"level":"pass","title":"All :total announced prefixes are RPKI valid.","params":{"total":10}},{"level":"pass","title":"Every announced prefix has an IRR route object.","params":[]},{"level":"info","title":":left upstreams and peers, :right downstream networks seen.","params":{"left":2,"right":6}}],"data":{"asn":42083,"holder":"GUNEYDOGUTELEKOM Guneydogu Telekom int.bil. ve ilt. hiz. tic. ltd. sti.","announced":true,"v4":10,"v6":0,"prefixes":["185.208.100.0/24","185.208.101.0/24","185.208.102.0/24","185.208.103.0/24","188.132.163.0/24","188.132.203.0/24","188.132.214.0/24","188.132.229.0/24","194.99.57.0/24","212.68.38.0/24"],"rpki":{"valid":10,"invalid":0,"not-found":0,"unchecked":0},"rpki_problems":[],"irr_missing":[],"irr_missing_count":0,"bogons":[],"upstreams":[{"asn":34984,"power":2303,"name":"Superonline"},{"asn":9121,"power":262,"name":"Turk Telekom"}],"left":2,"right":6},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS42083"},"summary":{"level":"warn","title":"No IPv6 prefixes announced.","params":[]}},"registration":{"status":"pass","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.db.ripe.net"}}],"data":{"query":"AS42083","looked_up":"AS42083","kind":"autnum","source":"https://rdap.db.ripe.net/autnum/42083","terms":"https://www.ripe.net/manage-ips-and-asns/db/support/documentation/terms/","summary":{"Name":"GUNEYDOGUTELEKOM","Handle":"AS42083","Range":"AS42083","Status":"active","Registered":"2017-06-16T07:17:47Z","Last changed":"2026-06-04T22:04:43Z","Abuse contact":"ripespam@kapsamnet.com.tr"},"entities":[{"roles":["registrant"],"kind":"org","name":"Guneydogu Telekom int.bil. ve ilt. hiz. tic. ltd. sti.","email":null},{"roles":["registrant"],"kind":"individual","name":"RIPE-NCC-END-MNT","email":null},{"roles":["registrant"],"kind":"individual","name":"tr-guneydogutelekom-1-mnt","email":null},{"roles":["abuse"],"kind":"group","name":"Abuse-C Role","email":"ripespam@kapsamnet.com.tr"}],"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"TR","country":"Turkey","date":"2017-06-16","status":"allocated","range":"AS42083","opaque_id":"fa139869-f469-4be0-ad0d-c2533bf03c7e","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS42083"},"summary":{"level":"pass","title":"Found at :server.","params":{"server":"rdap.db.ripe.net"}}},"peering":{"status":"warn","findings":[{"level":"pass","title":"AS:asn is in PeeringDB as :name.","params":{"asn":42083,"name":"Guneydogu Telekom"}},{"level":"info","title":"Peering policy: :policy.","params":{"policy":"Open"},"detail":"Peers with anyone at a shared location, usually without a contract."},{"level":"info","title":"No internet exchange ports are listed.","params":[]},{"level":"warn","title":"No IRR as-set is listed.","params":[],"detail":"Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.","fix":"Create an as-set in your RIR’s IRR database and add it to your PeeringDB record."}],"data":{"asn":42083,"net":{"id":34282,"name":"Guneydogu Telekom","aka":"","website":"http://www.kapsamnet.com.tr","looking_glass":"","route_server":"","irr_as_set":"","info_type":"Cable/DSL/ISP","info_prefixes4":1530,"info_prefixes6":6,"info_traffic":"300-500Gbps","info_ratio":"Mostly Inbound","info_scope":"Europe","info_unicast":true,"info_ipv6":false,"info_never_via_route_servers":true,"ix_count":0,"fac_count":0,"policy_url":"","policy_general":"Open","policy_locations":"Not Required","policy_ratio":false,"policy_contracts":"Not Required","updated":"2025-02-25T07:47:11Z"},"ix_count":0,"capacity":0,"ix":[],"ix_total":0,"fac":[],"fac_total":0,"poc":[{"role":"NOC","email":"noc@guneydogutelekom.com.tr"},{"role":"Public Relations","email":"info@kapsamnet.com.tr"}],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"42083"},"summary":{"level":"warn","title":"No IRR as-set is listed.","params":[]}}},"fixes":[{"level":"warn","title":"No IPv6 prefixes announced.","params":[],"detail":"Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.","fix":"Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.","section":"routing"},{"level":"warn","title":"No IRR as-set is listed.","params":[],"detail":"Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.","fix":"Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.","section":"peering"}]},"url":"https://thenetworkery.com/tools/network-report?query=AS42083"}