Skip to main content

AS38942

GRONET-AS

ORG-Gs31-RIPE

Registry

Authoritative registration data

AS number
38942
Name
GRONET-AS
Organisation
ORG-Gs31-RIPE
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

0

Total announced

12

Announced prefixes

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

Prefixes announced by AS38942
87.239.40.0/21 IPv4 /21 not checked
87.239.40.0/22 IPv4 /22 not checked
87.239.44.0/22 IPv4 /22 not checked
87.239.40.0/23 IPv4 /23 not checked
87.239.40.0/24 IPv4 /24 not checked
87.239.41.0/24 IPv4 /24 not checked
87.239.42.0/24 IPv4 /24 not checked
87.239.43.0/24 IPv4 /24 not checked
87.239.44.0/24 IPv4 /24 not checked
87.239.45.0/24 IPv4 /24 not checked
87.239.46.0/24 IPv4 /24 not checked
87.239.47.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 AS38942
Address families
EPIX.Katowice — IPv4
TPIX PL 8,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 AS38942 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS38942 in AS paths

Observed upstreams
Families
AS48626 QUARTO-AS 182 559
v4
AS5617 TPNET 242 364
v4
AS50607 EPIX-KTW-GlobalMix 101 130
v4
AS24482 SGGS-AS-AP 2 92
v4
AS33891 CORE-BACKBONE 10 39
v4
AS28917 Fiord-AS 3 12
v4
AS201054 EPIX-PolMix 11 11
v4
AS6204 ZET-NET 1 6
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS38942 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 12
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.