Skip to main content

AS8387

T-SYSTEMS-AT

Rennweg 97-99

Registry

Authoritative registration data

AS number
8387
Name
T-SYSTEMS-AT
Organisation
Rennweg 97-99
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

18

IPv6 prefixes

3

Total announced

21

Announced prefixes

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

Prefixes announced by AS8387
164.3.0.0/16 IPv4 /16 not checked
212.166.96.0/19 IPv4 /19 not checked
212.31.64.0/19 IPv4 /19 not checked
92.61.208.0/20 IPv4 /20 not checked
46.17.224.0/21 IPv4 /21 not checked
185.49.176.0/22 IPv4 /22 not checked
212.166.122.0/23 IPv4 /23 not checked
213.162.64.0/23 IPv4 /23 not checked
216.120.174.0/23 IPv4 /23 not checked
193.162.45.0/24 IPv4 /24 not checked
193.46.45.0/24 IPv4 /24 not checked
194.247.47.0/24 IPv4 /24 not checked
207.244.212.0/24 IPv4 /24 not checked
212.166.108.0/24 IPv4 /24 not checked
212.166.113.0/24 IPv4 /24 not checked
212.166.115.0/24 IPv4 /24 not checked
212.95.17.0/24 IPv4 /24 not checked
213.162.78.0/24 IPv4 /24 not checked
2001:9d0::/32 IPv6 /32 not checked
2001:678:554::/48 IPv6 /48 not checked
2001:678:5a8::/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 AS8387
Address families
VIX 20,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 AS8387 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

24 networks seen before AS8387 in AS paths

Observed upstreams
Families
AS1764 NEXTLAYER-AS 997 3,644
v4 v6
AS3320 DTAG 309 2,243
v4 v6
AS6939 HURRICANE 443 1,404
v4 v6
AS9002 RETN-AS 74 476
v4 v6
AS8218 NEO-ASN 11 207
v4 v6
AS3303 SWISSCOM 25 164
v4
AS13030 INIT7 13 144
v4 v6
AS14840 ASN14840 10 115
v4
AS47147 AS-ANX 7 114
v4 v6
AS48362 TKSWF-AS 8 101
v4 v6
AS5405 20 91
v4 v6
AS33891 CORE-BACKBONE 21 72
v4 v6
AS41327 FIBERTELECOM-AS 10 46
v4
AS50629 LWLCOM 8 37
v4 v6
AS22356 4 24
v4
AS6204 5 23
v4
AS6663 5 23
v4
AS9498 BBIL-AP 5 23
v4
AS15958 5 23
v4
AS8412 3 18
v4
AS15576 2 12
v4
AS263444 1 12
v4
AS15935 HA-VEL-LOCAL-AS 1 6
v4
AS29208 1 6
v4

No rows match “”.

Showing of

Observed downstreams

6 networks seen after AS8387 in AS paths

Observed downstreams
Families
AS214075 306 776
v4
AS211351 260 366
v6
AS35552 274 349
v4
AS43522 273 349
v4
AS205478 272 348
v4
AS203813 49 58
v4

No rows match “”.

Showing of

Uncertain adjacencies

16 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS59890 7 56
v4 v6
AS47692 6 54
v4 v6
AS49544 i3Dnet 6 54
v4 v6
AS51184 6 54
v4 v6
AS212483 level86 5 46
v4
AS40994 8 30
v4 v6
AS3212 7 28
v4 v6
AS6720 7 28
v4 v6
AS31510 IKB-AS 7 28
v4 v6
AS215628 7 28
v4 v6
AS34288 6 27
v4 v6
AS35369 6 27
v4 v6
AS13004 5 23
v4
AS13237 LAMBDANET-AS 5 23
v4
AS29049 5 23
v4
AS198150 SIACOM-AS 5 23
v4

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.