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.

AS135100 · 1 second ago

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

JSON Docs

Warning: AS135100 (MOL-AS-AP) announces 2 IPv4 and 0 IPv6 prefixes. 4 warnings

AS page	AS135100
Holder	MOL-AS-AP - Maxnet Online Limited
Allocation	APNIC, Bangladesh (BD), allocated 2016-02-15
Prefixes (IPv4 / IPv6)	2 / 0
RPKI valid	0% (0 / 2)
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
2 of 2 announced prefixes have no ROA (RPKI not found): 103.209.81.0/24, 103.209.83.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 AS135100 and a max length equal to the prefix length:
```
103.209.81.0/24 AS135100 max-length /24
103.209.83.0/24 AS135100 max-length /24
```
Open in RPKI / ROA validator Guide
Warning
2 of 2 announced prefixes have no IRR route object: 103.209.83.0/24, 103.209.81.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 AS135100 in your RIR’s IRR database (or RADB).
```
route: 103.209.83.0/24
origin: AS135100

route: 103.209.81.0/24
origin: AS135100
```
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: AS135100 announces 2 IPv4 and 0 IPv6 prefixes.
Warning: No IPv6 prefixes announced.
Warning: 2 of 2 announced prefixes have no ROA (RPKI not found): 103.209.81.0/24, 103.209.83.0/24.
Warning: 2 of 2 announced prefixes have no IRR route object: 103.209.83.0/24, 103.209.81.0/24.
Info: One upstream or peer seen (AS17806): an outage there takes the whole network off the internet.

Holder	MOL-AS-AP - Maxnet Online Limited
IPv4 prefixes	2
IPv6 prefixes	0
RPKI	2 not found
Without IRR route object	2
Downstream networks	0

Routes to fix

Prefix	RPKI
103.209.81.0/24	No ROA
103.209.83.0/24	No ROA

Upstreams and peers seen to the left 1

AS17806 Mango Teleservices Limited

Announced prefixes 2

103.209.81.0/24 103.209.83.0/24

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

Open in ASN & BGP prefix lookup

Registration Found at rdap.apnic.net.

Pass: Found at rdap.apnic.net.

Name	MOL-AS-AP
Handle	AS135100
Range	AS135100
Country	BD
Status	active
Registered	2016-02-15T11:32:06Z
Last changed	2020-09-22T08:01:54Z
Abuse contact	atik@bdigw.com

Allocation

Registry (RIR)	APNIC
Country	Bangladesh (BD)
Delegated on	2016-02-15
Status	Allocated
Delegated range	AS135100

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

Contacts

Role	Name	Email
technical, administrative	Faysal Ahmed	faysal.ahmed@maxnetonlinebd.com
abuse	IRT-MOL-BD	atik@bdigw.com
registrant	Maxnet Online Limited	techisp@maxnetonlinebd.com

Source: https://rdap.apnic.net/autnum/135100. Registration data from rdap.apnic.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