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.

AS265094 · 0 seconds ago

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

JSON Docs

Warning: AS265094 (AS265094) announces 4 IPv4 and 0 IPv6 prefixes. 4 warnings

AS page	AS265094
Holder	AS265094 - NET PARAISO
Allocation	LACNIC, Brazil (BR), allocated 2016-07-14
Prefixes (IPv4 / IPv6)	4 / 0
RPKI valid	0% (0 / 4)
Upstreams and peers	1

What to fix

Warning

No IPv6 prefixes announced.

Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

Open in ASN & BGP prefix lookup
Warning
4 of 4 announced prefixes have no ROA (RPKI not found): 170.254.12.0/24, 170.254.13.0/24, 170.254.14.0/24, 170.254.15.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 AS265094 and a max length equal to the prefix length:
```
170.254.12.0/24 AS265094 max-length /24
170.254.13.0/24 AS265094 max-length /24
170.254.14.0/24 AS265094 max-length /24
170.254.15.0/24 AS265094 max-length /24
```
Open in RPKI / ROA validator Guide
Warning
4 of 4 announced prefixes have no IRR route object: 170.254.12.0/24, 170.254.14.0/24, 170.254.13.0/24, 170.254.15.0/24.

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 AS265094 in your RIR’s IRR database (or RADB).
```
route: 170.254.12.0/24
origin: AS265094

route: 170.254.14.0/24
origin: AS265094

route: 170.254.13.0/24
origin: AS265094
```
Open in ASN & BGP prefix lookup
Warning

PeeringDB did not answer: HTTP 404

Fix: Try again in a minute.

Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.

Pass: AS265094 announces 4 IPv4 and 0 IPv6 prefixes.
Warning: No IPv6 prefixes announced.
Warning: 4 of 4 announced prefixes have no ROA (RPKI not found): 170.254.12.0/24, 170.254.13.0/24, 170.254.14.0/24, 170.254.15.0/24.
Warning: 4 of 4 announced prefixes have no IRR route object: 170.254.12.0/24, 170.254.14.0/24, 170.254.13.0/24, 170.254.15.0/24.
Info: One upstream or peer seen (AS52783): an outage there takes the whole network off the internet.

Holder	AS265094 - NET PARAISO
IPv4 prefixes	4
IPv6 prefixes	0
RPKI	4 not found
Without IRR route object	4
Downstream networks	0

Routes to fix

Prefix	RPKI
170.254.12.0/24	No ROA
170.254.13.0/24	No ROA
170.254.14.0/24	No ROA
170.254.15.0/24	No ROA

Upstreams and peers seen to the left 1

AS52783 ALCANS TELECOM LTDA

Announced prefixes 4

170.254.12.0/24 170.254.13.0/24 170.254.14.0/24 170.254.15.0/24

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.

Name	ASN265094
Handle	265094
Range	AS265094
Country	BR
Registered	2016-07-14T11:56:06Z
Last changed	2016-07-14T11:56:06Z
Abuse contact	alexandre@netparaiso.com

Allocation

Registry (RIR)	LACNIC
Country	Brazil (BR)
Delegated on	2016-07-14
Status	Allocated
Delegated range	AS265094

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

Contacts

Role	Name	Email
registrant	NET PARAISO
administrative, abuse	NET PARAISO TELECOM LTDA	alexandre@netparaiso.com

Source: https://rdap.lacnic.net/rdap/autnum/265094. 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 PeeringDB did not answer: HTTP 404

Warning: PeeringDB did not answer: HTTP 404

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup