Skip to main content

AS49633

MGK-AS

Kilinskiego 1b

Registry

Authoritative registration data

AS number
49633
Name
MGK-AS
Organisation
Kilinskiego 1b
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

2

Total announced

5

Announced prefixes

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

Prefixes announced by AS49633
92.63.32.0/20 IPv4 /20 not checked
185.106.168.0/22 IPv4 /22 RPKI not found
185.13.144.0/22 IPv4 /22 not checked
2a02:f3c0::/29 IPv6 /29 RPKI not found
2a0b:a80::/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 AS49633
Address families
EPIX.Warszawa — IPv4 · IPv6
Equinix Warsaw — 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 AS49633 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS49633 in AS paths

Observed upstreams
Families
AS20804 ASN-TELENERGO 190 616
v4 v6
AS6939 HURRICANE 40 72
v4 v6
AS12741 AS-NETIA 21 42
v4
AS29632 NASSIST-AS 2 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS49633 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 4
v4 v6
AS49544 i3Dnet 1 4
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.