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

AS266298 ·

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

Warning: AS266298 (AS266298) announces 3 IPv4 and 1 IPv6 prefixes. 3 warnings

AS pageAS266298
HolderAS266298 - MWA INTERNET. COM LTDA - ME
AllocationLACNIC, Brazil (BR), allocated 2016-10-14
Prefixes (IPv4 / IPv6)3 / 1
RPKI valid0% (0 / 4)
Upstreams and peers11
Peering policyOpen

What to fix

  1. Warning

    4 of 4 announced prefixes have no ROA (RPKI not found): 170.78.172.0/22, 170.78.172.0/23, 170.78.174.0/23, 2804:35a4::/32.

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

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

    170.78.172.0/22 AS266298 max-length /22
    170.78.172.0/23 AS266298 max-length /23
    170.78.174.0/23 AS266298 max-length /23
    2804:35a4::/32 AS266298 max-length /32

    Open in RPKI / ROA validator Guide

  2. Warning

    1 of 4 announced prefixes have no IRR route object: 170.78.172.0/23.

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

    route: 170.78.172.0/23
    origin: AS266298

    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 4 of 4 announced prefixes have no ROA (RPKI not found): 170.78.172.0/22, 170.78.172.0/23, 170.78.174.0/23, 2804:35a4::/32.
  • Pass: AS266298 announces 3 IPv4 and 1 IPv6 prefixes.
  • Warning: 4 of 4 announced prefixes have no ROA (RPKI not found): 170.78.172.0/22, 170.78.172.0/23, 170.78.174.0/23, 2804:35a4::/32.
  • Warning: 1 of 4 announced prefixes have no IRR route object: 170.78.172.0/23.
  • Info: 11 upstreams and peers, 0 downstream networks seen.
HolderAS266298 - MWA INTERNET. COM LTDA - ME
IPv4 prefixes3
IPv6 prefixes1
RPKI4 not found
Without IRR route object1
Downstream networks0
Routes to fix
PrefixRPKI
170.78.172.0/22 No ROA
170.78.172.0/23 No ROA
170.78.174.0/23 No ROA
2804:35a4::/32 No ROA

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

Open in ASN & BGP prefix lookup
Registration Found at rdap.lacnic.net.
  • Pass: Found at rdap.lacnic.net.
NameASN266298
Handle266298
RangeAS266298
CountryBR
Registered2016-10-14T11:41:21Z
Last changed2025-07-31T09:23:40Z
Abuse contactengenharia@mwainternet.com.br
Allocation
Registry (RIR)LACNIC
CountryBrazil (BR)
Delegated on2016-10-14
StatusAllocated
Delegated rangeAS266298

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

Contacts
RoleNameEmail
registrant MWA INTERNET. COM LTDA - ME
administrative, abuse MWA INTERNET. COM LTDA - ME engenharia@mwainternet.com.br

Source: https://rdap.lacnic.net/rdap/autnum/266298. Registration data from rdap.lacnic.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: AS266298 is in PeeringDB as MWA INTERNET. COM LTDA - ME.
  • Info: Peering policy: Open.
  • Info: Present at 1 internet exchanges with 1 ports (10G in total).
  • Warning: No public NOC, policy or technical contact.
NetworkMWA INTERNET. COM LTDA - ME (MWA INTERNET)
AS numberAS266298
TypeCable/DSL/ISP, South America
Websitehttp://www.mwainternet.com.br
IRR as-setAS-MWAINTERNET
Prefixes (IPv4 / IPv6)7 / 3
Traffic5-10Gbps, Heavy Inbound
Peering policyOpen
Policy URLhttps://bgp.he.net/AS266298#_whois
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2025-11-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup