{"tool":"network-report","status":"warn","input":{"query":"AS3582"},"findings":[{"level":"warn","text":"AS3582 (UONET) announces 5 IPv4 and 2 IPv6 prefixes.","title":"AS3582 (UONET) announces 5 IPv4 and 2 IPv6 prefixes.","params":{"query":"AS3582","who":"AS3582 (UONET)","v4":5,"v6":2}},{"level":"warn","text":"7 of 7 announced prefixes have no ROA (RPKI not found): 128.223.0.0/16, 163.41.128.0/17, 184.171.0.0/17, 207.98.0.0/18, 207.98.72.0/21 (+2).","title":"7 of 7 announced prefixes have no ROA (RPKI not found): 128.223.0.0/16, 163.41.128.0/17, 184.171.0.0/17, 207.98.0.0/18, 207.98.72.0/21 (+2).","params":{"count":7,"total":7,"list":"128.223.0.0/16, 163.41.128.0/17, 184.171.0.0/17, 207.98.0.0/18, 207.98.72.0/21 (+2)","asn":3582},"detail":"Without a ROA, networks cannot tell your routes from a hijack.","fix":"Create a ROA for each at your RIR portal, with origin AS3582 and a max length equal to the prefix length:","record":"128.223.0.0/16 AS3582 max-length /16\n163.41.128.0/17 AS3582 max-length /17\n184.171.0.0/17 AS3582 max-length /17\n207.98.0.0/18 AS3582 max-length /18\n207.98.72.0/21 AS3582 max-length /21\n2001:468:d01::/48 AS3582 max-length /48\n2607:8400::/32 AS3582 max-length /32"},{"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":"AS3582","kind":"asn","special":null,"allocation":{"rir":"arin","registry":"ARIN","cc":"US","country":"United States","date":"1994-05-11","status":"assigned","range":"AS3582","opaque_id":"5395ad8c1f13948854ab880ef8ccab72","special":null},"verdict":{"level":"warn","title":":who announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"query":"AS3582","who":"AS3582 (UONET)","v4":5,"v6":2}},"seconds":2,"sections":{"routing":{"status":"warn","findings":[{"level":"pass","title":"AS:asn announces :v4 IPv4 and :v6 IPv6 prefixes.","params":{"asn":3582,"v4":5,"v6":2}},{"tool":["rpki",{"prefix":"128.223.0.0/16","asn":"3582"}],"guide":"create-rpki-roas","level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":7,"total":7,"list":"128.223.0.0/16, 163.41.128.0/17, 184.171.0.0/17, 207.98.0.0/18, 207.98.72.0/21 (+2)","asn":3582},"detail":"Without a ROA, networks cannot tell your routes from a hijack.","fix":"Create a ROA for each at your RIR portal, with origin AS:asn and a max length equal to the prefix length:","record":"128.223.0.0/16 AS3582 max-length /16\n163.41.128.0/17 AS3582 max-length /17\n184.171.0.0/17 AS3582 max-length /17\n207.98.0.0/18 AS3582 max-length /18\n207.98.72.0/21 AS3582 max-length /21\n2001:468:d01::/48 AS3582 max-length /48\n2607:8400::/32 AS3582 max-length /32"},{"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":3701}}],"data":{"asn":3582,"holder":"UONET - University of Oregon","announced":true,"v4":5,"v6":2,"prefixes":["128.223.0.0/16","163.41.128.0/17","184.171.0.0/17","207.98.0.0/18","207.98.72.0/21","2001:468:d01::/48","2607:8400::/32"],"rpki":{"not-found":7,"valid":0,"invalid":0,"unchecked":0},"rpki_problems":[{"prefix":"128.223.0.0/16","state":"not-found"},{"prefix":"163.41.128.0/17","state":"not-found"},{"prefix":"184.171.0.0/17","state":"not-found"},{"prefix":"207.98.0.0/18","state":"not-found"},{"prefix":"207.98.72.0/21","state":"not-found"},{"prefix":"2001:468:d01::/48","state":"not-found"},{"prefix":"2607:8400::/32","state":"not-found"}],"irr_missing":[],"irr_missing_count":0,"bogons":[],"upstreams":[{"asn":3701,"power":476,"name":"Link Oregon"}],"left":1,"right":0},"title":"Routing and RPKI","tool":"bgp","tool_input":{"query":"AS3582"},"summary":{"level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":7,"total":7,"list":"128.223.0.0/16, 163.41.128.0/17, 184.171.0.0/17, 207.98.0.0/18, 207.98.72.0/21 (+2)","asn":3582}}},"registration":{"status":"pass","findings":[{"level":"pass","title":"Found at :server.","params":{"server":"rdap.arin.net"}}],"data":{"query":"AS3582","looked_up":"AS3582","kind":"autnum","source":"https://rdap.arin.net/registry/autnum/3582","terms":"https://www.arin.net/resources/registry/whois/tou/","summary":{"Name":"UONET","Handle":"AS3582","Range":"AS3582","Status":"active","Registered":"1994-05-11T00:00:00-04:00","Last changed":"2024-06-13T18:42:35-04:00","Abuse contact":"abuse@uoregon.edu"},"entities":[{"roles":["registrant"],"kind":"org","name":"University of Oregon","email":null},{"roles":["technical"],"kind":"individual","name":"Daniel Vance","email":"dvance@uoregon.edu"},{"roles":["abuse"],"kind":"group","name":"UOnet Abuse Desk","email":"abuse@uoregon.edu"},{"roles":["technical"],"kind":"individual","name":"Jose Alfredo Dominguez","email":"jad@uoregon.edu"},{"roles":["noc"],"kind":"group","name":"UOnet NOC","email":"uonethelp@uoregon.edu"}],"allocation":{"rir":"arin","registry":"ARIN","cc":"US","country":"United States","date":"1994-05-11","status":"assigned","range":"AS3582","opaque_id":"5395ad8c1f13948854ab880ef8ccab72","special":null}},"title":"Registration","tool":"whois","tool_input":{"query":"AS3582"},"summary":{"level":"pass","title":"Found at :server.","params":{"server":"rdap.arin.net"}}},"peering":{"status":"warn","findings":[{"level":"pass","title":"AS:asn is in PeeringDB as :name.","params":{"asn":3582,"name":"University of Oregon"}},{"level":"info","title":"Peering policy: :policy.","params":{"policy":"Selective"},"detail":"Peers when the traffic exchange makes sense to them; contact them with your traffic figures."},{"level":"info","title":"Present at :ix internet exchanges with :ports ports (:capacity in total).","params":{"ix":1,"ports":1,"capacity":"0M"}},{"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":3582,"net":{"id":13480,"name":"University of Oregon","aka":"University of Oregon","website":"http://www.uoregon.edu","looking_glass":"","route_server":"","irr_as_set":"","info_type":"Educational/Research","info_prefixes4":7,"info_prefixes6":2,"info_traffic":"","info_ratio":"Not Disclosed","info_scope":"Not Disclosed","info_unicast":true,"info_ipv6":true,"info_never_via_route_servers":false,"ix_count":1,"fac_count":0,"policy_url":"","policy_general":"Selective","policy_locations":"Not Required","policy_ratio":false,"policy_contracts":"Not Required","updated":"2022-07-27T05:33:21Z"},"ix_count":1,"capacity":0,"ix":[],"ix_total":1,"fac":[],"fac_total":0,"poc":[],"missing":[]},"title":"PeeringDB","tool":"peeringdb","tool_input":{"asn":"3582"},"summary":{"level":"warn","title":"No IRR as-set is listed.","params":[]}}},"fixes":[{"tool":["rpki",{"prefix":"128.223.0.0/16","asn":"3582"}],"guide":"create-rpki-roas","level":"warn","title":":count of :total announced prefixes have no ROA (RPKI not found): :list.","params":{"count":7,"total":7,"list":"128.223.0.0/16, 163.41.128.0/17, 184.171.0.0/17, 207.98.0.0/18, 207.98.72.0/21 (+2)","asn":3582},"detail":"Without a ROA, networks cannot tell your routes from a hijack.","fix":"Create a ROA for each at your RIR portal, with origin AS:asn and a max length equal to the prefix length:","record":"128.223.0.0/16 AS3582 max-length /16\n163.41.128.0/17 AS3582 max-length /17\n184.171.0.0/17 AS3582 max-length /17\n207.98.0.0/18 AS3582 max-length /18\n207.98.72.0/21 AS3582 max-length /21\n2001:468:d01::/48 AS3582 max-length /48\n2607:8400::/32 AS3582 max-length /32","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=AS3582"}