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.

AS21280 · 0 seconds ago

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

JSON Docs

Warning: AS21280 (Liquid Telecommunications Operations Li…) announces 3 IPv4 and 0 IPv6 prefixes. 5 warnings

AS page	AS21280
Holder	Liquid Telecommunications Operations Limited - Liquid Telecommunications Operations Limited
Allocation	AFRINIC, Mauritius (MU), allocated 2015-02-02
Prefixes (IPv4 / IPv6)	3 / 0
RPKI valid	0% (0 / 3)
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
3 of 3 announced prefixes have no ROA (RPKI not found): 41.173.184.0/22, 41.173.184.0/23, 41.173.186.0/23.

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

Fix: Create a ROA for each at your RIR portal, with origin AS21280 and a max length equal to the prefix length:
```
41.173.184.0/22 AS21280 max-length /22
41.173.184.0/23 AS21280 max-length /23
41.173.186.0/23 AS21280 max-length /23
```
Open in RPKI / ROA validator Guide
Warning
2 of 3 announced prefixes have no IRR route object: 41.173.186.0/23, 41.173.184.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 AS21280 in your RIR’s IRR database (or RADB).
```
route: 41.173.186.0/23
origin: AS21280

route: 41.173.184.0/23
origin: AS21280
```
Open in ASN & BGP prefix lookup
Warning

No abuse contact is published for AS21280.

Other networks send reports of spam, attacks and hacked machines to the abuse contact. Without one, reports go nowhere and blocklists may list the whole range.

Fix: Add an abuse contact to the registration: abuse-c in the RIPE database, an Abuse POC at ARIN, an abuse mailbox (IRT) at APNIC, AFRINIC or LACNIC.

Open in WHOIS / RDAP 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: AS21280 announces 3 IPv4 and 0 IPv6 prefixes.
Warning: No IPv6 prefixes announced.
Warning: 3 of 3 announced prefixes have no ROA (RPKI not found): 41.173.184.0/22, 41.173.184.0/23, 41.173.186.0/23.
Warning: 2 of 3 announced prefixes have no IRR route object: 41.173.186.0/23, 41.173.184.0/23.
Info: One upstream or peer seen (AS30844): an outage there takes the whole network off the internet.

Holder	Liquid Telecommunications Operations Limited - Liquid Telecommunications Operations Limited
IPv4 prefixes	3
IPv6 prefixes	0
RPKI	3 not found
Without IRR route object	2
Downstream networks	0

Routes to fix

Prefix	RPKI
41.173.184.0/22	No ROA
41.173.184.0/23	No ROA
41.173.186.0/23	No ROA

Upstreams and peers seen to the left 1

AS30844 Liquid Intelligent Technologies

Announced prefixes 3

41.173.184.0/22 41.173.184.0/23 41.173.186.0/23

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

Open in ASN & BGP prefix lookup

Registration No abuse contact is published for AS21280.

Pass: Found at rdap.db.ripe.net.
Warning: No abuse contact is published for AS21280.

Name	ORG-LTOL1-AFRINIC
Handle	AS21280
Range	AS21280
Status	active
Registered	2015-02-02T11:55:00Z
Last changed	2026-10-23T07:06:00Z

Allocation

Registry (RIR)	AFRINIC
Country	Mauritius (MU)
Delegated on	2015-02-02
Status	Allocated
Delegated range	AS21280

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	Liquid Telecommunications Operations Limited	rob.davelaar@liquidtelecom.mu

Source: https://rdap.db.ripe.net/autnum/21280. 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 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