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

155.103.1.0/24 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=155.103.1.0%2F24"
JSON Docs

Warning: 155.103.1.0/24 is announced by AS401682 (DIALWAVE). 3 warnings

Announced as155.103.1.0/24
Origin ASAS401682 DIALWAVE
HolderDialwave, Inc.
AllocationARIN, United States (US), allocated 2026-04-02
Size256 addresses
Abuse contactsupport@dialwave.com

What to fix

  1. Warning

    No IRR route object for 155.103.1.0/24 with origin AS401682.

    Many networks build their prefix filters from IRR data; without a route object some of them drop the route.

    Fix: Create a route object in your RIR’s IRR database (or RADB):

    route: 155.103.1.0/24
    origin: AS401682

    Open in ASN & BGP prefix lookup

  2. Warning

    Seen by only 20% of RIPE RIS peers.

    Partial visibility points to filtering, a missing IRR route object, or an RPKI problem.

    Open in ASN & BGP prefix lookup

  3. Warning

    Reverse DNS is not delegated for 155.103.1.0/24, so its addresses have no PTR records.

    Mail receivers look up the PTR of the sending address and reject or spam-score mail without one; traceroutes and logs show bare numbers.

    Fix: Create the reverse zones (domain objects for in-addr.arpa or ip6.arpa) at your RIR, pointing at your nameservers, or ask your provider to set PTR records.

    Open in DNS lookup

Checks

Routing and RPKI No IRR route object for 155.103.1.0/24 with origin AS401682.
  • Pass: Announced as 155.103.1.0/24 by AS401682.
  • Pass: 155.103.1.0/24 from AS401682 is RPKI valid.
  • Warning: No IRR route object for 155.103.1.0/24 with origin AS401682.
  • Warning: Seen by only 20% of RIPE RIS peers.
  • Info: The ROA 155.103.0.0/22 AS401682 allows announcements up to /24.
Route155.103.1.0/24
Origin ASAS401682 DIALWAVE - Dialwave, Inc. RPKI valid
Visibility (RIS peers)65 / 320
First seen2026-04-26
ROAs covering this prefix
ROA prefixMax lengthOrigin AS
155.103.0.0/22 /24 AS401682

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is not delegated for 155.103.1.0/24, so its addresses have no PTR records.
  • Warning: Reverse DNS is not delegated for 155.103.1.0/24, so its addresses have no PTR records.
Reverse zones 1
ZoneNameservers
1.103.155.in-addr.arpa Not delegated
Open in DNS lookup
Registration Found at rdap.arin.net.
  • Pass: Found at rdap.arin.net.
NameDIALWAVE
HandleNET-155-103-0-0-1
Range155.103.0.0 – 155.103.3.255
Statusactive
Registered2026-04-02T09:52:12-04:00
Last changed2026-04-02T09:52:12-04:00
Abuse contactsupport@dialwave.com
Allocation
Registry (RIR)ARIN
CountryUnited States (US)
Delegated on2026-04-02
StatusAllocated
Delegated range155.103.0.0/22 (155.103.0.0 – 155.103.3.255)

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

Contacts
RoleNameEmail
registrant Dialwave, Inc.

Source: https://rdap.arin.net/registry/ip/155.103.1.0/24. 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 public NOC, policy or technical contact.
  • Pass: AS401682 is in PeeringDB as Dialwave.
  • Info: Peering policy: Open.
  • Info: Present at 2 internet exchanges with 2 ports (0M in total).
  • Warning: No public NOC, policy or technical contact.

About the network that announces this space, so not in the fix list.

NetworkDialwave
AS numberAS401682
TypeNSP, Global
Websitehttps://dialwave.com
IRR as-setAS-DIALWAVE
Prefixes (IPv4 / IPv6)7 / 10
TrafficBalanced
Peering policyOpen
Policy URLhttps://www.peeringdb.com/asn/401682
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-04-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup