{"tool":"network-report","status":"warn","input":{"query":"AS45905"},"findings":[{"level":"warn","text":"AS45905 (STARGATE-AS-AP) announces 32 IPv4 and 1 IPv6 prefixes.","title":"AS45905 (STARGATE-AS-AP) announces 32 IPv4 and 1 IPv6 prefixes.","params":{"query":"AS45905","who":"AS45905 (STARGATE-AS-AP)","v4":32,"v6":1}},{"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."},{"level":"warn","text":"No public NOC, policy or technical contact.","title":"No public NOC, policy or technical contact.","params":{},"detail":"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."}],"data":{"query":"AS45905","kind":"asn","special":null,"allocation":{"rir":"apnic","registry":"APNIC","cc":"BD","country":"Bangladesh","date":"2009-08-31","status":"allocated","range":"AS45905","opaque_id":"A916A171","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS45905","who":"AS45905 (STARGATE-AS-AP)","v4":32,"v6":1}},"seconds":0.20000000000000001,"sections":{"routing":{"status":"pass","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":45905,"v4":32,"v6":1}},{"level":"pass","title":"All :total announced prefixes are RPKI valid.","params":{"total":33}},{"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":3,"right":6}}],"data":{"asn":45905,"holder":"STARGATE-AS-AP - Stargate Communications Ltd.","announced":true,"v4":32,"v6":1,"prefixes":["45.118.244.0/24","45.118.245.0/24","45.118.246.0/24","45.126.74.0/24","45.126.75.0/24","103.59.36.0/24","103.59.37.0/24","103.59.38.0/24","103.59.39.0/24","103.65.134.0/24","103.65.135.0/24","103.77.100.0/24","103.96.36.0/24","103.96.37.0/24","103.96.38.0/24","103.96.39.0/24","116.212.185.0/24","119.15.156.0/24","119.15.157.0/24","123.253.196.0/24","123.253.198.0/24","123.253.199.0/24","123.253.215.0/24","160.22.150.0/24","180.148.208.0/24","180.148.209.0/24","180.148.210.0/24","180.148.211.0/24","180.148.212.0/24","180.148.213.0/24","180.148.214.0/24","180.148.215.0/24","2405:86c0::/32"],"rpki":{"valid":33,"invalid":0,"not-found":0,"unchecked":0},"rpki_problems":[],"irr_missing":[],"irr_missing_count":0,"bogons":[],"upstreams":[{"asn":58717,"power":2960,"name":"Summit Communications Limited AS58717"},{"asn":10075,"power":290,"name":"Fiber@Home Global Limited"},{"asn":17494,"power":275,"name":"Bangladesh Telecommunications"}],"left":3,"right":6},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS45905"},"summary":{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":45905,"v4":32,"v6":1}}},"registration":{"status":"pass","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.apnic.net"}}],"data":{"query":"AS45905","looked_up":"AS45905","kind":"autnum","source":"https://rdap.apnic.net/autnum/45905","terms":"https://www.apnic.net/about-apnic/whois_search/about/termsofuse/","summary":{"Name":"STARGATE-AS-AP","Handle":"AS45905","Range":"AS45905","Country":"BD","Status":"active","Registered":"2009-08-31T02:57:20Z","Last changed":"2020-07-07T04:52:58Z","Abuse contact":"srtoufiq@hotmail.com"},"entities":[{"roles":["abuse"],"kind":"group","name":"IRT-STARGATE-BD","email":"srtoufiq@hotmail.com"},{"roles":["administrative","technical"],"kind":"group","name":"Stargate communications Ltd administrator","email":"srtoufiq@hotmail.com"},{"roles":["registrant"],"kind":"org","name":"Stargate Communications Ltd.","email":"srtoufiq@hotmail.com"}],"allocation":{"rir":"apnic","registry":"APNIC","cc":"BD","country":"Bangladesh","date":"2009-08-31","status":"allocated","range":"AS45905","opaque_id":"A916A171","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS45905"},"summary":{"level":"pass","title":"Found at :server.","params":{"server":"rdap.apnic.net"}}},"peering":{"status":"warn","findings":[{"level":"pass","title":"AS:asn is in PeeringDB as :name.","params":{"asn":45905,"name":"Stargate Communications"}},{"level":"info","title":"Peering policy: :policy.","params":{"policy":"Open"},"detail":"Peers with anyone at a shared location, usually without a contract."},{"level":"info","title":"Present at :ix internet exchanges with :ports ports (:capacity in total).","params":{"ix":2,"ports":2,"capacity":"10G"}},{"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."},{"level":"warn","title":"No public NOC, policy or technical contact.","params":[],"detail":"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."}],"data":{"asn":45905,"net":{"id":21069,"name":"Stargate Communications","aka":"","website":"http://www.stargatebd.com","looking_glass":"","route_server":"","irr_as_set":"","info_type":"Cable/DSL/ISP","info_prefixes4":10752,"info_prefixes6":0,"info_traffic":"10-20Gbps","info_ratio":"Mostly Outbound","info_scope":"Regional","info_unicast":true,"info_ipv6":false,"info_never_via_route_servers":false,"ix_count":2,"fac_count":0,"policy_url":"","policy_general":"Open","policy_locations":"Not Required","policy_ratio":false,"policy_contracts":"Not Required","updated":"2025-10-27T08:29:21Z"},"ix_count":2,"capacity":10000,"ix":[],"ix_total":2,"fac":[],"fac_total":0,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"45905"},"summary":{"level":"warn","title":"No IRR as-set is listed.","params":[]}}},"fixes":[{"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"},{"level":"warn","title":"No public NOC, policy or technical contact.","params":[],"detail":"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.","section":"peering"}]},"url":"https://thenetworkery.com/tools/network-report?query=AS45905"}