{"tool":"network-report","status":"warn","input":{"query":"AS42183"},"findings":[{"level":"warn","text":"AS42183 (net360 NET 360 S.A.R.L) announces 4 IPv4 and 0 IPv6 prefixes.","title":"AS42183 (net360 NET 360 S.A.R.L) announces 4 IPv4 and 0 IPv6 prefixes.","params":{"query":"AS42183","who":"AS42183 (net360 NET 360 S.A.R.L)","v4":4,"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."},{"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":"AS42183","kind":"asn","special":null,"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"LB","country":"Lebanon","date":"2014-12-24","status":"allocated","range":"AS42183","opaque_id":"2773e152-9830-4d5f-b28e-902fed6bfa31","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS42183","who":"AS42183 (net360 NET 360 S.A.R.L)","v4":4,"v6":0}},"seconds":0,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":42183,"v4":4,"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":4}},{"level":"pass","title":"Every announced prefix has an IRR route object.","params":[]},{"level":"info","title":"One upstream or peer seen (AS:upstream): an outage there takes the whole network off the internet.","params":{"upstream":42020}}],"data":{"asn":42183,"holder":"net360 NET 360 S.A.R.L","announced":true,"v4":4,"v6":0,"prefixes":["185.82.96.0/24","185.82.97.0/24","185.82.98.0/24","185.82.99.0/24"],"rpki":{"valid":4,"invalid":0,"not-found":0,"unchecked":0},"rpki_problems":[],"irr_missing":[],"irr_missing_count":0,"bogons":[],"upstreams":[{"asn":42020,"power":507,"name":"LibanTelecom"}],"left":1,"right":0},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS42183"},"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":"AS42183","looked_up":"AS42183","kind":"autnum","source":"https://rdap.db.ripe.net/autnum/42183","terms":"https://www.ripe.net/manage-ips-and-asns/db/support/documentation/terms/","summary":{"Name":"net360","Handle":"AS42183","Range":"AS42183","Status":"active","Registered":"2014-12-24T11:39:32Z","Last changed":"2026-03-23T13:31:08Z","Abuse contact":"noc@net360.net.lb"},"entities":[{"roles":["registrant"],"kind":"individual","name":"NOC-Net360","email":null},{"roles":["registrant"],"kind":"org","name":"NET 360 S.A.R.L","email":null},{"roles":["registrant"],"kind":"individual","name":"RIPE-NCC-END-MNT","email":null},{"roles":["abuse"],"kind":"group","name":"ABUSE Net360","email":"noc@net360.net.lb"}],"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"LB","country":"Lebanon","date":"2014-12-24","status":"allocated","range":"AS42183","opaque_id":"2773e152-9830-4d5f-b28e-902fed6bfa31","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS42183"},"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":42183,"name":"NET 360"}},{"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."},{"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."},{"level":"info","title":"The record was last updated :date.","params":{"date":"2022-07-27"},"detail":"Peers rely on it for max-prefix limits and contacts; check it is still right."}],"data":{"asn":42183,"net":{"id":12495,"name":"NET 360","aka":"","website":"http://net360.net.lb","looking_glass":"","route_server":"","irr_as_set":"","info_type":"","info_prefixes4":4,"info_prefixes6":1,"info_traffic":"1-5Gbps","info_ratio":"Heavy Inbound","info_scope":"Middle East","info_unicast":true,"info_ipv6":true,"info_never_via_route_servers":false,"ix_count":0,"fac_count":0,"policy_url":"","policy_general":"Open","policy_locations":"Required - EU","policy_ratio":false,"policy_contracts":"Private Only","updated":"2022-07-27T05:34:25Z"},"ix_count":0,"capacity":0,"ix":[],"ix_total":0,"fac":[],"fac_total":0,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"42183"},"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"},{"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=AS42183"}