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

45.138.220.0/22 ·

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

Warning: 45.138.220.0/22 is announced by AS49434 (FBWNETWORKS). 7 warnings

Announced as45.138.220.0/22
Origin ASAS49434 FBWNETWORKS
AllocationRIPE NCC, Czechia (CZ), allocated 2019-08-08
Size1,024 addresses

What to fix

  1. Warning

    45.138.220.0/22 from AS49434 is RPKI not found: no ROA covers it.

    Routes without a ROA are still accepted almost everywhere, but nothing protects them from a hijack.

    Fix: Create a ROA for this prefix with origin AS49434 and a max length equal to the prefix length.

    prefix: 45.138.220.0/22
    origin: AS49434
    max-length: 22

    Open in RPKI / ROA validator Guide

  2. Warning

    45.138.222.0/23 from AS39522 is RPKI not found: no ROA covers it. 45.138.222.0/23

    Routes without a ROA are still accepted almost everywhere, but nothing protects them from a hijack.

    Fix: Create a ROA for this prefix with origin AS39522 and a max length equal to the prefix length.

    prefix: 45.138.222.0/23
    origin: AS39522
    max-length: 23

    Open in RPKI / ROA validator Guide

  3. Warning

    45.138.221.0/24 from AS211028 is RPKI not found: no ROA covers it. 45.138.221.0/24

    Routes without a ROA are still accepted almost everywhere, but nothing protects them from a hijack.

    Fix: Create a ROA for this prefix with origin AS211028 and a max length equal to the prefix length.

    prefix: 45.138.221.0/24
    origin: AS211028
    max-length: 24

    Open in RPKI / ROA validator Guide

  4. Warning

    45.138.222.0/24 from AS39522 is RPKI not found: no ROA covers it. 45.138.222.0/24

    Routes without a ROA are still accepted almost everywhere, but nothing protects them from a hijack.

    Fix: Create a ROA for this prefix with origin AS39522 and a max length equal to the prefix length.

    prefix: 45.138.222.0/24
    origin: AS39522
    max-length: 24

    Open in RPKI / ROA validator Guide

  5. Warning

    45.138.223.0/24 from AS39522 is RPKI not found: no ROA covers it. 45.138.223.0/24

    Routes without a ROA are still accepted almost everywhere, but nothing protects them from a hijack.

    Fix: Create a ROA for this prefix with origin AS39522 and a max length equal to the prefix length.

    prefix: 45.138.223.0/24
    origin: AS39522
    max-length: 24

    Open in RPKI / ROA validator Guide

  6. Warning

    No IRR route object for 45.138.220.0/22 with origin AS49434.

    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: 45.138.220.0/22
    origin: AS49434

    Open in ASN & BGP prefix lookup

  7. Warning

    Reverse DNS is not delegated for 45.138.220.0/22, 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 45.138.220.0/22 from AS49434 is RPKI not found: no ROA covers it.
  • Pass: Announced as 45.138.220.0/22 by AS49434.
  • Warning: 45.138.220.0/22 from AS49434 is RPKI not found: no ROA covers it.
  • Warning: 45.138.222.0/23 from AS39522 is RPKI not found: no ROA covers it. 45.138.222.0/23
  • Warning: 45.138.221.0/24 from AS211028 is RPKI not found: no ROA covers it. 45.138.221.0/24
  • Warning: 45.138.222.0/24 from AS39522 is RPKI not found: no ROA covers it. 45.138.222.0/24
  • Warning: 45.138.223.0/24 from AS39522 is RPKI not found: no ROA covers it. 45.138.223.0/24
  • Warning: No IRR route object for 45.138.220.0/22 with origin AS49434.
  • Pass: Seen by 100% of RIPE RIS peers.
Route45.138.220.0/22
Origin ASAS49434 FBWNETWORKS FBW NETWORKS SAS No ROA
Visibility (RIS peers)322 / 322
First seen2020-06-10
More-specific routes 4
More-specific routeOrigin ASRPKI
45.138.222.0/23 AS39522 No ROA
45.138.221.0/24 AS211028 No ROA
45.138.222.0/24 AS39522 No ROA
45.138.223.0/24 AS39522 No ROA

Source: RIPEstat (RIPE NCC RIS, Routinator)

Open in ASN & BGP prefix lookup
Reverse DNS Reverse DNS is not delegated for 45.138.220.0/22, so its addresses have no PTR records.
  • Warning: Reverse DNS is not delegated for 45.138.220.0/22, so its addresses have no PTR records.
Reverse zones 4
ZoneNameservers
220.138.45.in-addr.arpa Not delegated
221.138.45.in-addr.arpa Not delegated
222.138.45.in-addr.arpa Not delegated
223.138.45.in-addr.arpa Not delegated
Open in DNS lookup
Registration Not found at the registry.
PeeringDB No public NOC, policy or technical contact.
  • Pass: AS49434 is in PeeringDB as FBW Networks.
  • Info: Peering policy: Open.
  • Info: Present at 14 internet exchanges with 15 ports (1.6T in total).
  • Warning: No public NOC, policy or technical contact.

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

NetworkFBW Networks (FIBERWAY, FBW)
AS numberAS49434
TypeNSP, Europe
Websitehttps://as49434.net
IRR as-setRIPE::AS-HHOSTING
Prefixes (IPv4 / IPv6)10000 / 10000
Traffic500-1000Gbps, Balanced
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2026-07-15

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup