Skip to main content

AS56628

StormMedia

STORMmedia sp. z o.o.

Registry

Authoritative registration data

AS number
56628
Name
StormMedia
Organisation
STORMmedia sp. z o.o.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS56628
192.162.148.0/22 IPv4 /22 not checked
77.73.16.0/22 IPv4 /22 not checked
2a13:4f40::/32 IPv6 /32 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 AS56628
Address families
EPIX.Katowice 40,000 Mbps IPv4 · IPv6
EPIX.Warszawa 40,000 Mbps IPv4
IX.LODZ.PL: LAN 1 40,000 Mbps IPv4
TPIX PL 40,000 Mbps IPv4

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

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS56628 in AS paths

Observed upstreams
Families
AS62081 477 991
v4
AS50607 131 170
v4 v6
AS201054 EPIX-PolMix 115 161
v4 v6
AS6204 1 2
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS56628 in AS paths

Observed downstreams
Families
AS199787 258 347
v4

No rows match “”.

Showing of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 27
v4 v6
AS49544 i3Dnet 1 6
v4 v6
AS36236 NETACTUATE 1 3
v4 v6
AS28917 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.