Skip to main content

AS48626

QUARTO-AS

Mediasat s.c.

Registry

Authoritative registration data

AS number
48626
Name
QUARTO-AS
Organisation
Mediasat s.c.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

0

Total announced

7

Announced prefixes

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

Prefixes announced by AS48626
193.34.52.0/22 IPv4 /22 not checked
193.34.52.0/23 IPv4 /23 not checked
193.34.54.0/23 IPv4 /23 not checked
193.34.52.0/24 IPv4 /24 not checked
193.34.53.0/24 IPv4 /24 not checked
193.34.54.0/24 IPv4 /24 not checked
193.34.55.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 AS48626
Address families
EPIX.Katowice 20,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 AS48626 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS48626 in AS paths

Observed upstreams
Families
AS20804 ASN-TELENERGO 335 855
v4
AS50607 148 196
v4
AS24482 SGGS-AS-AP 2 73
v4
AS6204 7 20
v4
AS28917 3 7
v4
AS201054 3 3
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS48626 in AS paths

Observed downstreams
Families
AS38942 202 675
v4

No rows match “”.

Showing of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

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