{"tool":"network-report","status":"warn","input":{"query":"AS205187"},"findings":[{"level":"warn","text":"AS205187 (PL-PSJ-ISP) announces 1 IPv4 and 0 IPv6 prefixes.","title":"AS205187 (PL-PSJ-ISP) announces 1 IPv4 and 0 IPv6 prefixes.","params":{"query":"AS205187","who":"AS205187 (PL-PSJ-ISP)","v4":1,"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":"AS205187","kind":"asn","special":null,"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"PL","country":"Poland","date":"2017-10-19","status":"allocated","range":"AS205187","opaque_id":"d7002419-d79f-4f4d-b47d-9fa956db6be3","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS205187","who":"AS205187 (PL-PSJ-ISP)","v4":1,"v6":0}},"seconds":0.29999999999999999,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":205187,"v4":1,"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":1}},{"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":12618}}],"data":{"asn":205187,"holder":"PL-PSJ-ISP PSJ sp. z o.o.","announced":true,"v4":1,"v6":0,"prefixes":["185.226.248.0/22"],"rpki":{"valid":1,"invalid":0,"not-found":0,"unchecked":0},"rpki_problems":[],"irr_missing":[],"irr_missing_count":0,"bogons":[],"upstreams":[{"asn":12618,"power":269,"name":"MAN Bydgoszcz COM"}],"left":1,"right":0},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS205187"},"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":"AS205187","looked_up":"AS205187","kind":"autnum","source":"https://rdap.db.ripe.net/autnum/205187","terms":"https://www.ripe.net/manage-ips-and-asns/db/support/documentation/terms/","summary":{"Name":"PL-PSJ-ISP","Handle":"AS205187","Range":"AS205187","Status":"active","Registered":"2017-10-19T13:40:47Z","Last changed":"2018-09-04T12:06:29Z","Abuse contact":"abuse@psj.com.pl"},"entities":[{"roles":["registrant"],"kind":"org","name":"PSJ sp. z o.o.","email":null},{"roles":["registrant"],"kind":"individual","name":"PL-PSJ-MNT","email":null},{"roles":["registrant"],"kind":"individual","name":"RIPE-NCC-END-MNT","email":null},{"roles":["abuse"],"kind":"group","name":"Abuse-C Role","email":"abuse@psj.com.pl"}],"allocation":{"rir":"ripencc","registry":"RIPE NCC","cc":"PL","country":"Poland","date":"2017-10-19","status":"allocated","range":"AS205187","opaque_id":"d7002419-d79f-4f4d-b47d-9fa956db6be3","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS205187"},"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":205187,"name":"PSJ"}},{"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-09-16"},"detail":"Peers rely on it for max-prefix limits and contacts; check it is still right."}],"data":{"asn":205187,"net":{"id":30982,"name":"PSJ","aka":"","website":"","looking_glass":"","route_server":"","irr_as_set":"","info_type":"","info_prefixes4":0,"info_prefixes6":0,"info_traffic":"","info_ratio":"Not Disclosed","info_scope":"Not Disclosed","info_unicast":false,"info_ipv6":false,"info_never_via_route_servers":false,"ix_count":0,"fac_count":0,"policy_url":"","policy_general":"Open","policy_locations":"Not Required","policy_ratio":false,"policy_contracts":"Not Required","updated":"2022-09-16T22:55:15Z"},"ix_count":0,"capacity":0,"ix":[],"ix_total":0,"fac":[],"fac_total":0,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"205187"},"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=AS205187"}