Autonomous system
AS8819 PL-METROINTERNET
Hosting RIPE Network Services
Summary
Metro Internet Sp. z o.o.
isp residential legacy
PL-METROINTERNET is Metro Internet Sp. z o.o., a Polish regional access provider. It announces a compact, coherent block of RIPE space and delegates first-party reverse DNS across all of it.
What it's used for
Fixed broadband access. Sampled addresses resolve to the reversed-octet pattern N.N.N.N.rev.metrointernet.pl, and one sampled address lands squarely on bras.metrointernet.pl — a BRAS (Broadband Remote Access Server), the box that terminates subscriber PPPoE/DHCP sessions. A BRAS in the middle of the address space is about as direct a statement as rDNS makes: this is an eyeball network handing addresses to end users.
Notable
- Four IPv4 prefixes totalling roughly 7,000 addresses, plus IPv6. Small and tidy — no scattered multi-RIR inventory, no third-party registrants.
- 13 observed BGP neighbours, which is a healthy amount of upstream and peering diversity for a network this size and suggests it does real regional interconnection rather than sitting behind a single transit link.
- One sampled address in
83.142.192.0/21resolves totaurus-rtr.iim.pl, a router name in a different domain — a normal sign of inherited or shared infrastructure between related Polish operators, not of address brokering.
Interesting
First seen in BGP in early 2007 with 91.189.24.0/21. The AS number itself is much older than that announcement, so the number and the current use are not the same vintage.
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
Recorded at 2 exchanges in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| TPIX - Internet Exchange | Warsaw, Poland | 195.149.233.26 |
| Equinix Internet Exchange Warsaw | Warsaw, Poland | 195.182.219.243 |
Transit providers
8 upstream, 0 downstream and 10 adjacent networks observed; most-used upstreams first.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-10, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 5 prefixes · 7.17K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| PL | Poland | 6 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS8819- Registry name
- PL-METROINTERNET
- Registrant
- MNT-METRO-INTERNET
- Abuse contact
- internet@metrointernet.pl
- Registered
- 2006-12-28
- Last changed
- 2026-09-24
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Metro Internet
- Network type
- Network Services
- Scope
- Regional
- Traffic ratio
- Mostly Inbound
- Peering policy
- Open
- IRR as-set
RIPE::AS-METROINTERNET- Present at
- 4 exchanges
- Facilities
- 4 facilities
- Website
- http://www.metrointernet.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 · 6 valid, 0 with no ROA
- ROAs
- 6 authorising AS8819
- ASPA
- no ASPA record
- IRR
- 100% registered · 6 of 6 announcements
- Route objects
- 7 naming AS8819
Reputation
Classification and threat
Hosting Datacenter or cloud provider. Addresses are servers, not people.
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: 431 networks and 1,775 prefixes, as published 2026-10-11. 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