Skip to content
thenetworkery

Network report

Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.

IP address, prefix or AS number

AS400317 · 

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS400317"
JSON Docs

Warning: AS400317 (ORCHEST) announces 15 IPv4 and 1 IPv6 prefixes. 4 warnings

AS pageAS400317
HolderORCHEST - GoldConnect
AllocationARIN, United States (US), assigned 2021-12-17
Prefixes (IPv4 / IPv6)15 / 1
RPKI valid6% (1 / 16)
Upstreams and peers0
Peering policyOpen

What to fix

  1. Warning

    10 of 16 announced prefixes have no ROA (RPKI not found): 63.160.134.0/24, 63.160.140.0/24, 63.160.145.0/24, 63.160.151.0/24, 204.57.224.0/21 (+5).

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS400317 and a max length equal to the prefix length:

    63.160.134.0/24 AS400317 max-length /24
63.160.140.0/24 AS400317 max-length /24
63.160.145.0/24 AS400317 max-length /24
63.160.151.0/24 AS400317 max-length /24
204.57.224.0/21 AS400317 max-length /21
204.57.224.0/23 AS400317 max-length /23
204.57.224.0/24 AS400317 max-length /24
204.57.225.0/24 AS400317 max-length /24
204.57.226.0/24 AS400317 max-length /24
204.57.227.0/24 AS400317 max-length /24

    Open in RPKI / ROA validator Guide

  2. Warning

    7 of 16 announced prefixes have no IRR route object: 204.57.229.0/24, 204.57.226.0/24, 204.57.224.0/23, 204.57.227.0/24, 204.57.224.0/24 (+2).

    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 AS400317 in your RIR’s IRR database (or RADB).

    route: 204.57.229.0/24
origin: AS400317

route: 204.57.226.0/24
origin: AS400317

route: 204.57.224.0/23
origin: AS400317

    Open in ASN & BGP prefix lookup

  3. Warning

    No IRR as-set is listed.

    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.

    Open in PeeringDB lookup

  4. Warning

    No public NOC, policy or technical contact.

    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.

    Open in PeeringDB lookup

Checks

Routing and RPKI 10 of 16 announced prefixes have no ROA (RPKI not found): 63.160.134.0/24, 63.160.140.0/24, 63.160.145.0/24, 63.160.151.0/24, 204.57.224.0/21 (+5).
  • Pass: AS400317 announces 15 IPv4 and 1 IPv6 prefixes.
  • Warning: 10 of 16 announced prefixes have no ROA (RPKI not found): 63.160.134.0/24, 63.160.140.0/24, 63.160.145.0/24, 63.160.151.0/24, 204.57.224.0/21 (+5).
  • Info: 1 of 16 announced prefixes are RPKI valid.
  • Info: The RPKI state of 5 prefixes was not looked up (no ROA of AS400317 covers them; only the first 10 are checked).
  • Warning: 7 of 16 announced prefixes have no IRR route object: 204.57.229.0/24, 204.57.226.0/24, 204.57.224.0/23, 204.57.227.0/24, 204.57.224.0/24 (+2).
  • Info: 0 upstreams and peers, 0 downstream networks seen.
HolderORCHEST - GoldConnect
IPv4 prefixes15
IPv6 prefixes1
RPKI1 valid · 10 not found · 5 not looked up
Without IRR route object7
Downstream networks0
Routes to fix
PrefixRPKI
63.160.134.0/24 No ROA
63.160.140.0/24 No ROA
63.160.145.0/24 No ROA
63.160.151.0/24 No ROA
204.57.224.0/21 No ROA
204.57.224.0/23 No ROA
204.57.224.0/24 No ROA
204.57.225.0/24 No ROA
204.57.226.0/24 No ROA
204.57.227.0/24 No ROA

Announced prefixes 16

63.160.134.0/24 63.160.140.0/24 63.160.145.0/24 63.160.151.0/24 204.57.224.0/21 204.57.224.0/23 204.57.224.0/24 204.57.225.0/24 204.57.226.0/24 204.57.227.0/24 204.57.229.0/24 204.117.1.0/24 204.119.24.0/24 204.119.27.0/24 204.119.60.0/24 2602:f6cc::/36

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.arin.net.
  • Pass: Found at rdap.arin.net.
NameORCHEST
HandleAS400317
RangeAS400317
Statusactive
Registered2021-12-17T11:45:25-05:00
Last changed2026-09-28T12:06:10-04:00
Abuse contactmiguel.piacquadio@orchest.net
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2021-12-17
StatusAssigned
Delegated rangeAS400317

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant Orchest Technologies

Source: https://rdap.arin.net/registry/autnum/400317. Registration data from rdap.arin.net, shown under its terms of use (terms): not for marketing or bulk collection.

Open in WHOIS / RDAP lookup
PeeringDB No IRR as-set is listed.
  • Pass: AS400317 is in PeeringDB as GoldConnect.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2023-11-30.
NetworkGoldConnect
AS numberAS400317
Type, Not Disclosed
Websitehttp://goldconnect.com
Prefixes (IPv4 / IPv6)0 / 0
TrafficNot Disclosed
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2023-11-30

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup