Skip to main content

AS28889

LINZNET-AS

------------------------------

Registry

Authoritative registration data

AS number
28889
Name
LINZNET-AS
Organisation
------------------------------
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

17

IPv6 prefixes

0

Total announced

17

Announced prefixes

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

Prefixes announced by AS28889
80.66.32.0/19 IPv4 /19 not checked
85.193.128.0/20 IPv4 /20 not checked
85.193.176.0/20 IPv4 /20 not checked
193.46.100.0/22 IPv4 /22 not checked
193.187.252.0/23 IPv4 /23 not checked
193.46.102.0/23 IPv4 /23 not checked
91.206.236.0/23 IPv4 /23 not checked
185.135.16.0/24 IPv4 /24 not checked
185.135.17.0/24 IPv4 /24 not checked
185.135.18.0/24 IPv4 /24 not checked
185.135.19.0/24 IPv4 /24 not checked
185.54.208.0/24 IPv4 /24 not checked
185.54.209.0/24 IPv4 /24 not checked
193.187.254.0/24 IPv4 /24 not checked
193.46.101.0/24 IPv4 /24 not checked
91.206.236.0/24 IPv4 /24 not checked
91.206.237.0/24 IPv4 /24 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 AS28889
Address families
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 100,000 Mbps IPv4 · IPv6
VIX 100,000 Mbps IPv4 · 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 AS28889 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

56 networks seen before AS28889 in AS paths

No rows match “”.

Showing of

Observed downstreams

4 networks seen after AS28889 in AS paths

Observed downstreams
Families
AS43848 693 3,364
v4
AS211510 RDI-AT 328 493
v4
AS208350 267 359
v4
AS204419 88 107
v4

No rows match “”.

Showing of

Uncertain adjacencies

61 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.