{"tool":"network-report","status":"warn","input":{"query":"AS50084"},"findings":[{"level":"warn","text":"AS50084 (RAPID-LINK-AS) announces 7 IPv4 and 1 IPv6 prefixes.","title":"AS50084 (RAPID-LINK-AS) announces 7 IPv4 and 1 IPv6 prefixes.","params":{"query":"AS50084","who":"AS50084 (RAPID-LINK-AS)","v4":7,"v6":1}},{"level":"warn","text":"3 of 8 announced prefixes have no IRR route object: 185.96.177.0/24, 185.96.179.0/24, 185.96.176.0/24.","title":"3 of 8 announced prefixes have no IRR route object: 185.96.177.0/24, 185.96.179.0/24, 185.96.176.0/24.","params":{"count":3,"total":8,"list":"185.96.177.0/24, 185.96.179.0/24, 185.96.176.0/24","asn":50084},"detail":"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 AS50084 in your RIR’s IRR database (or RADB).","record":"route: 185.96.177.0/24\norigin: AS50084\n\nroute: 185.96.179.0/24\norigin: AS50084\n\nroute: 185.96.176.0/24\norigin: AS50084"},{"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":"AS50084","kind":"asn","special":null,"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"MD","country":"Moldova","date":"2009-11-11","status":"allocated","range":"AS50084","opaque_id":"5ec28468-957a-498f-ba92-9043573d4c4a","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS50084","who":"AS50084 (RAPID-LINK-AS)","v4":7,"v6":1}},"seconds":0.40000000000000002,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":50084,"v4":7,"v6":1}},{"level":"pass","title":"All :total announced prefixes are RPKI valid.","params":{"total":8}},{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":3,"total":8,"list":"185.96.177.0/24, 185.96.179.0/24, 185.96.176.0/24","asn":50084},"detail":"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 AS:asn in your RIR’s IRR database (or RADB).","record":"route: 185.96.177.0/24\norigin: AS50084\n\nroute: 185.96.179.0/24\norigin: AS50084\n\nroute: 185.96.176.0/24\norigin: AS50084"},{"level":"info","title":":left upstreams and peers, :right downstream networks seen.","params":{"left":3,"right":8}}],"data":{"asn":50084,"holder":"RAPID-LINK-AS S.A.\"Rapid Link\" S.R.L.","announced":true,"v4":7,"v6":1,"prefixes":["185.96.176.0/22","185.96.176.0/24","185.96.177.0/24","185.96.178.0/24","185.96.179.0/24","194.247.164.0/24","194.247.165.0/24","2a07:4140::/29"],"rpki":{"valid":8,"invalid":0,"not-found":0,"unchecked":0},"rpki_problems":[],"irr_missing":["185.96.177.0/24","185.96.179.0/24","185.96.176.0/24"],"irr_missing_count":3,"bogons":[],"upstreams":[{"asn":5606,"power":836,"name":"GTS Telecom"},{"asn":9002,"power":523,"name":"RETN"},{"asn":14840,"power":6,"name":"BR.Digital"}],"left":3,"right":8},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS50084"},"summary":{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":3,"total":8,"list":"185.96.177.0/24, 185.96.179.0/24, 185.96.176.0/24","asn":50084}}},"registration":{"status":"pass","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.db.ripe.net"}}],"data":{"query":"AS50084","looked_up":"AS50084","kind":"autnum","source":"https://rdap.db.ripe.net/autnum/50084","terms":"https://www.ripe.net/manage-ips-and-asns/db/support/documentation/terms/","summary":{"Name":"RAPID-LINK-AS","Handle":"AS50084","Range":"AS50084","Status":"active","Registered":"2009-11-11T10:00:39Z","Last changed":"2025-11-22T08:59:21Z","Abuse contact":"noc@rapidlink.md"},"entities":[{"roles":["registrant"],"kind":"org","name":"S.A.\"Rapid Link\" S.R.L.","email":null},{"roles":["registrant"],"kind":"individual","name":"RAPID-LINK-MNT","email":null},{"roles":["registrant"],"kind":"individual","name":"RIPE-NCC-END-MNT","email":null},{"roles":["abuse"],"kind":"group","name":"Abuse-C Role","email":"noc@rapidlink.md"}],"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"MD","country":"Moldova","date":"2009-11-11","status":"allocated","range":"AS50084","opaque_id":"5ec28468-957a-498f-ba92-9043573d4c4a","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS50084"},"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":50084,"name":"RAPIDLINK SRL"}},{"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":1,"ports":1,"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":"info","title":"The record was last updated :date.","params":{"date":"2022-11-17"},"detail":"Peers rely on it for max-prefix limits and contacts; check it is still right."}],"data":{"asn":50084,"net":{"id":31532,"name":"RAPIDLINK SRL","aka":"","website":"http://rapidlink.md","looking_glass":"","route_server":"","irr_as_set":"","info_type":"Cable/DSL/ISP","info_prefixes4":10,"info_prefixes6":4,"info_traffic":"5-10Gbps","info_ratio":"Mostly Inbound","info_scope":"Regional","info_unicast":true,"info_ipv6":true,"info_never_via_route_servers":false,"ix_count":1,"fac_count":2,"policy_url":"http://rapidlink.md","policy_general":"Open","policy_locations":"Preferred","policy_ratio":false,"policy_contracts":"Not Required","updated":"2022-11-17T22:55:18Z"},"ix_count":1,"capacity":10000,"ix":[],"ix_total":1,"fac":[],"fac_total":2,"poc":[{"role":"Abuse","email":"noc@rapidlink.md"},{"role":"NOC","email":"noc@rapidlink.md"}],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"50084"},"summary":{"level":"warn","title":"No IRR as-set is listed.","params":[]}}},"fixes":[{"level":"warn","title":":count of :total announced prefixes have no IRR route object: :list.","params":{"count":3,"total":8,"list":"185.96.177.0/24, 185.96.179.0/24, 185.96.176.0/24","asn":50084},"detail":"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 AS:asn in your RIR’s IRR database (or RADB).","record":"route: 185.96.177.0/24\norigin: AS50084\n\nroute: 185.96.179.0/24\norigin: AS50084\n\nroute: 185.96.176.0/24\norigin: AS50084","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=AS50084"}