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.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Warning: AS51394 (AKASHANET-AS) announces 2 IPv4 and 0 IPv6 prefixes. 2 warnings
| AS page | AS51394 |
|---|---|
| Holder | AKASHANET-AS Akasha.net Sp. z o.o. |
| Allocation | RIPE NCC, Poland (PL), allocated 2010-08-12 |
| Prefixes (IPv4 / IPv6) | 2 / 0 |
| RPKI valid | 100% (2 / 2) |
| Upstreams and peers | 1 |
| Peering policy | Open |
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.
-
Warning
No IRR as-set is listed.
Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.
Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.
Checks
Routing and RPKI No IPv6 prefixes announced.
- Pass: AS51394 announces 2 IPv4 and 0 IPv6 prefixes.
- Warning: No IPv6 prefixes announced.
- Pass: All 2 announced prefixes are RPKI valid.
- Pass: Every announced prefix has an IRR route object.
- Info: One upstream or peer seen (AS51465): an outage there takes the whole network off the internet.
| Holder | AKASHANET-AS Akasha.net Sp. z o.o. |
|---|---|
| IPv4 prefixes | 2 |
| IPv6 prefixes | 0 |
| RPKI | 2 valid |
| Downstream networks | 0 |
Upstreams and peers seen to the left 1
Announced prefixes 2
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.db.ripe.net.
- Pass: Found at rdap.db.ripe.net.
| Name | AKASHANET-AS |
|---|---|
| Handle | AS51394 |
| Range | AS51394 |
| Status | active |
| Registered | 2010-08-12T11:51:05Z |
| Last changed | 2025-11-19T12:06:15Z |
| Abuse contact | robert.lipinski@akashanet.pl |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | Poland (PL) |
| Delegated on | 2010-08-12 |
| Status | Allocated |
| Delegated range | AS51394 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| registrant | FIXMAP-MNT | |
| registrant | lir-pl-enformatel-1-MNT | |
| registrant | MNT-AKASHA | |
| registrant | Akasha.net Sp. z o.o. | |
| registrant | RIPE-NCC-END-MNT | |
| abuse | Abuse-C Role | robert.lipinski@akashanet.pl |
Source: https://rdap.db.ripe.net/autnum/51394. 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 lookupPeeringDB No IRR as-set is listed.
- Pass: AS51394 is in PeeringDB as Akasha.net Sp. z o.o..
- Info: Peering policy: Open.
- Info: No internet exchange ports are listed.
- Warning: No IRR as-set is listed.
- Info: The record was last updated 2022-07-27.
| Network | Akasha.net Sp. z o.o. |
|---|---|
| AS number | AS51394 |
| Type | Cable/DSL/ISP, Europe |
| Website | http://www.akashanet.pl |
| Prefixes (IPv4 / IPv6) | 2 / 0 |
| Traffic | 5-10Gbps, Balanced |
| Peering policy | Open |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2022-07-27 |
| NOC | robert.lipinski@akashanet.pl |
|---|---|
| Sales | biuro@akashanet.pl |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup