Skip to main content

AS48025

AS_ISLANDNET

ISLAND-SERWIS-NET MIROSLAW GORCZAKOWSKI

Registry

Authoritative registration data

AS number
48025
Name
AS_ISLANDNET
Organisation
ISLAND-SERWIS-NET MIROSLAW GORCZAKOWSKI
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS48025
45.88.96.0/24 IPv4 /24 not checked
2001:678:c98::/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

Internet Exchange memberships listed for AS48025
Address families
EPIX.Warszawa 1,000 Mbps IPv4 · IPv6
TPIX PL 10,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 AS48025 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS48025 in AS paths

Observed upstreams
Families
AS5617 TPNET 197 326
v4 v6
AS6939 HURRICANE 118 171
v4 v6
AS24482 SGGS-AS-AP 2 19
v4 v6
AS33891 CORE-BACKBONE 7 11
v4 v6
AS28917 Fiord-AS 2 4
v4 v6
AS6204 ZET-NET 1 1
v4
AS201054 EPIX-PolMix 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS48025 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 2
v4 v6

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.