Skip to main content

AS200258

MIKEBRESSEM

AS6939 - Hurricane Electric

Registry

Authoritative registration data

AS number
200258
Name
MIKEBRESSEM
Organisation
AS6939 - Hurricane Electric
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

1

Total announced

1

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS200258
2001:67c:b50::/48 IPv6 /48 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS200258
Address families
LOCIX DUSSELDORF: Peering LAN 1,000 Mbps IPv6
LOCIX FRANKFURT: Peering LAN 1,000 Mbps IPv6
ixFabric - Dusseldorf 1,000 Mbps IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS200258 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS200258 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 151 210
v6
AS41051 FREETRANSIT 21 26
v6
AS34549 MEER-AS 11 15
v6
AS34872 Servperso_Systems 10 12
v6
AS199938 NETZWERGE 11 11
v6
AS25091 IP-Max 2 4
v6
AS8298 IPNG 2 2
v6
AS48646 STEFAN6 1 1
v6
AS401753 BIXCE 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS200258 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.