Skip to main content

AS202177

MEGA-NET-AS

Dominik Drozdz trading as Mega-Net

Registry

Authoritative registration data

AS number
202177
Name
MEGA-NET-AS
Organisation
Dominik Drozdz trading as Mega-Net
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS202177
185.117.84.0/22 IPv4 /22 not checked
217.173.202.0/24 IPv4 /24 not checked
217.173.203.0/24 IPv4 /24 not checked
217.173.204.0/24 IPv4 /24 not checked
2a06:8340::/29 IPv6 /29 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 AS202177
Address families
EPIX.Katowice 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 AS202177 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS202177 in AS paths

Observed upstreams
Families
AS25584 OPOLMAN-AS-COM 279 1,352
v4
AS24482 SGGS-AS-AP 2 40
v4 v6
AS1820 1 1
v6
AS20473 1 1
v6

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS202177 in AS paths

Observed downstreams
Families
AS199381 11 12
v4

No rows match “”.

Showing of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 8
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.