Autonomous system
AS15507 IT3GNS-P4-AS
Unclassified RIPE
Summary
P4
business infrastructure
The registry lookup failed, so nothing can be said about who holds the one block.
What it's used for
- A company network. One IPv4
/24and one IPv6/48announced from Poland, two hundred and fifty-six addresses, through a single observed BGP neighbour.
Notable
- The registry lookup for the single IPv4 block failed. That is a failed fetch, not an empty record, so the netname and registrant here are unknown rather than absent.
- The AS handle strings together a technology abbreviation, a service abbreviation and the company code before the usual suffix.
- The IPv6 prefix comes from a range the registry uses for assignments that travel with the holder rather than with a provider.
- Three addresses were queried for reverse DNS and none returned a name.
- Routing history first records this network several years after the numbers around it appeared.
Interesting
- A failed lookup is worth stating plainly, because the alternative reading, that the block has no registration, would be wrong and would matter. The record may be complete and simply unreachable.
- One
/24alongside a/48is the modern minimum: the smallest globally routable piece of each protocol, held so the network can be reached under its own number. - A single upstream means this network is reachable only while that one relationship holds. For a footprint this small that is usually a cost decision taken on purpose, but it is still a single point of failure.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Transit providers
1 upstream, 0 downstream and 2 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS39603 | P4 Sp. z o.o. | 90 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-18, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 1 prefixes · 256 addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| PL | Poland | 2 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS15507- Registry name
- IT3GNS-P4-AS
- Registrant
- IT3GNS-MNT
- Abuse contact
- abuse@play.pl
- Registered
- 2008-03-31
- Last changed
- 2019-06-28
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 100% valid · 2 valid, 0 with no ROA
- ROAs
- 2 authorising AS15507
- ASPA
- no ASPA record
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 2 naming AS15507
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 442 networks and 1,784 prefixes, as published 2026-10-19. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere