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

AS45474 ·

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

Warning: AS45474 (NEXUSGUARD-AS-AP) announces 89 IPv4 and 18 IPv6 prefixes. 3 warnings

AS pageAS45474
HolderNEXUSGUARD-AS-AP - Nexusguard Pte. Ltd.
AllocationAPNIC, Singapore (SG), allocated 2008-10-15
Prefixes (IPv4 / IPv6)89 / 18
RPKI valid97% (104 / 107)
Upstreams and peers88
Peering policySelective

What to fix

  1. Warning

    3 of 107 announced prefixes have no ROA (RPKI not found): 207.192.148.0/24, 207.192.186.0/24, 207.192.187.0/24.

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

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

    207.192.148.0/24 AS45474 max-length /24
    207.192.186.0/24 AS45474 max-length /24
    207.192.187.0/24 AS45474 max-length /24

    Open in RPKI / ROA validator Guide

  2. Warning

    17 of 107 announced prefixes have no IRR route object: 207.192.187.0/24, 2404:ae00:ffff::/48, 2404:ae00:ff87::/48, 2404:ae00::/48, 2404:ae00:15::/48 (+12).

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

    route: 207.192.187.0/24
    origin: AS45474
    
    route6: 2404:ae00:ffff::/48
    origin: AS45474
    
    route6: 2404:ae00:ff87::/48
    origin: AS45474

    Open in ASN & BGP prefix lookup

  3. 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 3 of 107 announced prefixes have no ROA (RPKI not found): 207.192.148.0/24, 207.192.186.0/24, 207.192.187.0/24.
  • Pass: AS45474 announces 89 IPv4 and 18 IPv6 prefixes.
  • Warning: 3 of 107 announced prefixes have no ROA (RPKI not found): 207.192.148.0/24, 207.192.186.0/24, 207.192.187.0/24.
  • Info: 104 of 107 announced prefixes are RPKI valid.
  • Warning: 17 of 107 announced prefixes have no IRR route object: 207.192.187.0/24, 2404:ae00:ffff::/48, 2404:ae00:ff87::/48, 2404:ae00::/48, 2404:ae00:15::/48 (+12).
  • Info: 88 upstreams and peers, 30 downstream networks seen.
HolderNEXUSGUARD-AS-AP - Nexusguard Pte. Ltd.
IPv4 prefixes89
IPv6 prefixes18
RPKI104 valid · 3 not found
Without IRR route object17
Downstream networks30
Routes to fix
PrefixRPKI
207.192.148.0/24 No ROA
207.192.186.0/24 No ROA
207.192.187.0/24 No ROA

Announced prefixes 107

27.126.194.0/24 27.126.195.0/24 27.126.199.0/24 27.126.200.0/24 27.126.201.0/24 27.126.202.0/24 27.126.203.0/24 27.126.205.0/24 27.126.206.0/24 27.126.208.0/24 27.126.210.0/24 27.126.211.0/24 27.126.212.0/24 27.126.215.0/24 27.126.216.0/24 27.126.217.0/24 27.126.219.0/24 27.126.225.0/24 27.126.226.0/24 27.126.231.0/24 27.126.233.0/24 27.126.234.0/24 27.126.235.0/24 27.126.236.0/24 27.126.237.0/24 27.126.238.0/24 27.126.239.0/24 27.126.240.0/24 27.126.241.0/24 27.126.242.0/24 27.126.245.0/24 27.126.246.0/24 27.126.247.0/24 27.126.248.0/24 27.126.249.0/24 27.126.250.0/24 27.126.251.0/24 27.126.252.0/24 27.126.253.0/24 27.126.254.0/24 45.116.40.0/24 45.116.41.0/24 45.116.42.0/24 45.116.43.0/24 74.52.5.0/24 103.3.24.0/24 103.3.26.0/24 103.3.27.0/24 113.21.194.0/24 113.21.199.0/24 113.21.200.0/24 113.21.202.0/24 113.21.204.0/24 113.21.205.0/24 113.21.206.0/24 113.21.208.0/24 113.21.213.0/24 113.21.214.0/24 113.21.215.0/24 113.21.217.0/24 113.21.218.0/24 113.21.219.0/24 113.21.220.0/24 113.21.223.0/24 122.11.181.0/24 122.11.183.0/24 122.11.184.0/24 122.11.185.0/24 122.11.186.0/24 167.179.206.0/24 167.179.207.0/24 180.233.160.0/24 180.233.161.0/24 180.233.165.0/24 180.233.167.0/24 180.233.171.0/24 180.233.172.0/24 180.233.174.0/24 180.233.175.0/24 180.233.176.0/24 180.233.177.0/24 180.233.182.0/24 180.233.184.0/24 180.233.187.0/24 180.233.190.0/24 180.233.191.0/24 207.192.148.0/24 207.192.186.0/24 207.192.187.0/24 2404:ae00:10::/48 2404:ae00:11::/48 2404:ae00:12::/48 2404:ae00:13::/48 2404:ae00:14::/48 2404:ae00:15::/48 2404:ae00:17::/48 2404:ae00:18::/48 2404:ae00:19::/48 2404:ae00:3266::/48 2404:ae00:3638::/48

Showing the first 100.

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

Open in ASN & BGP prefix lookup
Registration Found at rdap.apnic.net.
  • Pass: Found at rdap.apnic.net.
NameNEXUSGUARD-AS-AP
HandleAS45474
RangeAS45474
CountrySG
Statusactive
Registered2026-01-08T07:45:23Z
Last changed2026-01-08T07:47:09Z
Abuse contactabuse@nexusguard.com
Allocation
Registry (RIR)APNIC
CountrySingapore (SG)
Delegated on2008-10-15
StatusAllocated
Delegated rangeAS45474

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

Contacts
RoleNameEmail
registrant Nexusguard Pte. Ltd. peering@nexusguard.com
administrative, technical Nexusguard Pte Ltd administrator abuse@nexusguard.com
abuse IRT-NEXUSGUARD-SG abuse@nexusguard.com

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

Open in WHOIS / RDAP lookup
PeeringDB No public NOC, policy or technical contact.
  • Pass: AS45474 is in PeeringDB as Nexusguard.
  • Info: Peering policy: Selective.
  • Info: Present at 9 internet exchanges with 11 ports (1T in total).
  • Warning: No public NOC, policy or technical contact.
NetworkNexusguard (Nexusguard)
AS numberAS45474
TypeNetwork Services, Global
Websitehttps://www.nexusguard.com/
IRR as-setAS45474:AS-NEXUSGUARD
Prefixes (IPv4 / IPv6)1500 / 200
TrafficMostly Inbound
Peering policySelective
LocationsPreferred
Ratio requiredNo
ContractsNot Required
Last updated2026-01-19

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup