Autonomous system
AS16290 TARMAN Tarnow
Unclassified RIPE Cable/DSL/ISP
Summary
Tarnowski Osrodek Informacyjny
isp telecom business
Three answered addresses, three different reverse-name schemes, two different domains.
What it's used for
- A city information centre's network. Three IPv4 prefixes announced from Poland, no IPv6, eleven thousand two hundred and sixty-four addresses, through six observed BGP neighbours.
Notable
- Three of nine queried addresses answered, and no two follow quite the same rule. One is two letters for an address, then the third and fourth octets joined by a hyphen, on the network's own domain.
- The second replaces those two letters with a single letter for a host, keeping everything else identical, so one scheme has two prefixes depending on which range you land in.
- The third uses the first form but sits on the city government's domain, under a three-letter label for the municipal office.
- All three blocks share one netname scheme: a country code, the network's brand, and a full date. Two blocks share one date and the third is three years later.
- The holder field is an institution's name followed by a private individual's name, so the registry records a person alongside the organisation.
- The AS handle is the brand and the city, which is the only place the city is named outright.
Interesting
- A city network that serves the municipality from its own address space blurs a line most operators keep sharp. The council's hosts answer under the council's domain on the provider's addresses.
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.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-20, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 3 prefixes · 11.26K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| PL | Poland | 3 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS16290- Registry name
- TARMAN
- Registrant
- Tarnowski Osrodek Informacyjny Aleksander Rajski
- Abuse contact
- admin@tarman.pl
- Registered
- 1970-01-01
- Last changed
- 2017-11-15
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- TARMAN
- Also known as
- TARMAN
- Network type
- Cable/DSL/ISP
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- IRR as-set
RIPE::AS-TARMAN- Present at
- 1 exchanges
- Facilities
- 2 facilities
- Website
- https://tarman.pl
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 100% valid · 3 valid, 0 with no ROA
- ROAs
- 3 authorising AS16290
- ASPA
- no ASPA record
- IRR
- 100% registered · 3 of 3 announcements
- Route objects
- 4 naming AS16290
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,779 prefixes, as published 2026-10-21. 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