Autonomous system
AS200258 MIKEBRESSEM
Unclassified RIPE
Summary
Mike Bressem
individual ipv6 germany
The AS handle MIKEBRESSEM is held by Mike Bressem.
What it's used for
- The space carries a single IPv6 prefix,
2001:67c:b50::/48, with no IPv4 addresses announced. - With 18 observed neighbours against a single IPv6 prefix, the routing footprint suggests a small-scale network or individual presence rather than a large transit or access provider.
- The operator is an individual based in Germany, as indicated by the registry holder and PeeringDB information.
Notable
- The registry holder is Mike Bressem, consistent with the AS name.
- The address inventory consists solely of one IPv6 /48 block, indicating a minimal footprint.
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 |
|---|---|---|
| Local Internet Exchange Düsseldorf | Düsseldorf, Germany | 185.1.155.165 |
| Local Internet Exchange Frankfurt | Frankfurt, Germany | 185.1.167.208 |
Transit providers
8 upstream, 0 downstream and 8 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-26, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 0 prefixes · 0 addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| DE | Germany | 1 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS200258- Registry name
- MIKEBRESSEM
- Registrant
- MBR-MNT
- Abuse contact
- abuse@bressem.com
- Registered
- 2022-12-30
- Last changed
- 2026-05-13
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Mike Bressem
- Scope
- Europe
- Peering policy
- Open
- IRR as-set
AS-MBR- Present at
- 3 exchanges
- Website
- https://blog.bressem.com
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 · 1 valid, 0 with no ROA
- ROAs
- 1 authorising AS200258
- ASPA
- 5 declared providers
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 1 naming AS200258
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: 446 networks and 1,852 prefixes, as published 2026-10-27. 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