Skip to main content

AS203597

STEKSPB-AS

STEK LLC

Registry

Authoritative registration data

AS number
203597
Name
STEKSPB-AS
Organisation
STEK LLC
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

2

Total announced

4

Announced prefixes

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

Prefixes announced by AS203597
194.190.151.0/24 IPv4 /24 not checked
45.9.195.0/24 IPv4 /24 not checked
2a0e:1107:1::/48 IPv6 /48 not checked
2a0e:1107::/48 IPv6 /48 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS203597 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS203597 in AS paths

Observed upstreams
Families
AS3216 SOVAM-AS 98 232
v4 v6
AS20764 RASCOM-AS 89 175
v4 v6
AS57304 RETNRU-AS 64 162
v4 v6
AS51178 AVANTEL-SPB-AS 69 82
v4 v6
AS6939 HURRICANE 8 16
v4
AS25091 IP-Max 2 4
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS203597 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 8
v4
AS37721 ORG-VTS1-AFRINIC 1 2
v4
AS205112 PHILUNET 1 2
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.