Skip to main content

AS48822

UNIVERSUMNET-AS

-----------------------------------------------

Registry

Authoritative registration data

AS number
48822
Name
UNIVERSUMNET-AS
Organisation
-----------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS48822
95.171.0.0/19 IPv4 /19 RPKI valid
185.216.60.0/22 IPv4 /22 RPKI valid
2a02:2548::/32 IPv6 /32 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 AS48822
Address families
MSK-IX Moscow: MSK-IX peering network 5,000 Mbps IPv4 · IPv6
PITER-IX Frankfurt 4,000 Mbps IPv4
PITER-IX Helsinki 4,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 10,000 Mbps IPv4 · IPv6
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 4,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 AS48822 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS48822 in AS paths

Observed upstreams
Families
AS29076 CITYTELECOM-AS 175 292
v4 v6
AS57304 RETNRU-AS 110 199
v4 v6
AS1299 TWELVE99 52 103
v4 v6
AS35598 INETCOM 48 73
v4 v6
AS62255 BEMYLINK 39 47
v4 v6
AS25091 IP-Max 6 11
v4 v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS48822 in AS paths

Observed downstreams
Families
AS51183 ACOMPS-NET 160 188
v4

No rows match “”.

Showing – of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 8
v4 v6
AS37721 ORG-VTS1-AFRINIC 2 3
v4
AS49544 i3Dnet 2 3
v4
AS49673 TRUENETWORK 2 3
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.