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

AS49434 · 

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

Problem: AS49434 (FBWNETWORKS) announces 21 IPv4 and 7 IPv6 prefixes. 1 problem · 3 warnings

AS pageAS49434
HolderFBWNETWORKS FBW NETWORKS SAS
AllocationRIPE NCC, France (FR), allocated 2016-09-23
Prefixes (IPv4 / IPv6)21 / 7
RPKI valid82% (23 / 28)
Upstreams and peers54
Peering policyOpen

What to fix

  1. Problem

    2 of 28 announced prefixes are RPKI invalid: 2a0f:9240:1016::/48, 2a0f:9240:1021::/48.

    A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.

    Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.

    Open in RPKI / ROA validator Guide

  2. Warning

    3 of 28 announced prefixes have no ROA (RPKI not found): 45.138.220.0/22, 194.31.251.0/24, 2a12:8140::/30.

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

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

    45.138.220.0/22 AS49434 max-length /22
194.31.251.0/24 AS49434 max-length /24
2a12:8140::/30 AS49434 max-length /30

    Open in RPKI / ROA validator Guide

  3. Warning

    3 of 28 announced prefixes have no IRR route object: 45.138.220.0/22, 2a0f:9240:1021::/48, 2a0f:9240:1016::/48.

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

    route: 45.138.220.0/22
origin: AS49434

route6: 2a0f:9240:1021::/48
origin: AS49434

route6: 2a0f:9240:1016::/48
origin: AS49434

    Open in ASN & BGP prefix 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 2 of 28 announced prefixes are RPKI invalid: 2a0f:9240:1016::/48, 2a0f:9240:1021::/48.
  • Pass: AS49434 announces 21 IPv4 and 7 IPv6 prefixes.
  • Problem: 2 of 28 announced prefixes are RPKI invalid: 2a0f:9240:1016::/48, 2a0f:9240:1021::/48.
  • Warning: 3 of 28 announced prefixes have no ROA (RPKI not found): 45.138.220.0/22, 194.31.251.0/24, 2a12:8140::/30.
  • Info: 23 of 28 announced prefixes are RPKI valid.
  • Warning: 3 of 28 announced prefixes have no IRR route object: 45.138.220.0/22, 2a0f:9240:1021::/48, 2a0f:9240:1016::/48.
  • Info: 54 upstreams and peers, 1139 downstream networks seen.
HolderFBWNETWORKS FBW NETWORKS SAS
IPv4 prefixes21
IPv6 prefixes7
RPKI23 valid · 2 invalid · 3 not found
Without IRR route object3
Downstream networks1139
Routes to fix
PrefixRPKI
2a0f:9240:1016::/48 RPKI invalid
2a0f:9240:1021::/48 RPKI invalid
45.138.220.0/22 No ROA
194.31.251.0/24 No ROA
2a12:8140::/30 No ROA

Upstreams and peers seen to the left 54

AS6453 TATA Communications Ltd AS6939 Hurricane Electric AS33891 Core-Backbone AS9002 RETN AS6762 Telecom Italia Sparkle AS5511 Orange AS37468 Angola Cables AS137409 Global Secure Layer AS6830 Liberty Global AS20485 TransTelecom AS5405 Inter.link AS37100 SEACOM

Announced prefixes 28

37.44.236.0/24 37.44.237.0/24 45.138.220.0/22 79.110.237.0/24 87.232.79.0/24 89.31.210.0/24 91.238.181.0/24 95.173.62.0/24 170.39.219.0/24 185.142.52.0/24 185.142.54.0/24 185.142.55.0/24 185.177.45.0/24 185.177.46.0/24 185.177.47.0/24 185.198.20.0/22 193.177.162.0/24 193.177.182.0/24 193.178.0.0/24 194.31.251.0/24 217.119.141.0/24 2a0a:2f82::/32 2a0f:9240:1016::/48 2a0f:9240:1021::/48 2a0f:9240::/32 2a09:ca00::/29 2a12:8140::/30 2a13:bf80::/29

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

Open in ASN & BGP prefix lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameFBWNETWORKS
HandleAS49434
RangeAS49434
Statusactive
Registered2016-09-23T12:10:24Z
Last changed2026-10-30T07:02:18Z
Abuse contactabuse@fiberway.fr
Allocation
Registry (RIR)RIPE NCC
CountryFrance (FR)
Delegated on2016-09-23
StatusAllocated
Delegated rangeAS49434

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

Contacts
RoleNameEmail
registrant lir-fr-fbw-networks-1-MNT
registrant FBW NETWORKS SAS
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role abuse@fiberway.fr

Source: https://rdap.db.ripe.net/autnum/49434. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.

Open in WHOIS / RDAP lookup
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.
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