Skip to main content

AS48481

RYBALKA-AS

KINGISEPP-ONLINE Ltd.

Registry

Authoritative registration data

AS number
48481
Name
RYBALKA-AS
Organisation
KINGISEPP-ONLINE Ltd.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

0

Total announced

8

Announced prefixes

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

Prefixes announced by AS48481
31.132.208.0/20 IPv4 /20 not checked
94.231.144.0/20 IPv4 /20 not checked
91.211.44.0/22 IPv4 /22 not checked
217.64.152.0/23 IPv4 /23 not checked
217.64.154.0/23 IPv4 /23 not checked
5.59.184.0/23 IPv4 /23 not checked
185.32.67.0/24 IPv4 /24 not checked
185.50.149.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 AS48481
Address families
GNM-IX 20,000 Mbps IPv4
PITER-IX Frankfurt 10,000 Mbps IPv4
PITER-IX Helsinki 10,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 10,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 10,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 AS48481 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS48481 in AS paths

Observed upstreams
Families
AS50509 TRANSROUTE 152 1,544
v4
AS20764 RASCOM-AS 111 1,091
v4
AS44843 10 104
v4
AS25091 IP-Max 3 48
v4
AS47692 NESSUS 2 32
v4
AS50673 Serverius-as 2 16
v4
AS6204 ZET-NET 1 8
v4
AS6663 TTI-NET 1 8
v4
AS9198 KAZTELECOM-AS 1 8
v4
AS15958 CETIN_doo_AS 1 8
v4
AS42295 TBISS-AS 1 8
v4
AS60171 AFRIX-AS 1 8
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS48481 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

15 adjacencies that may be an artefact of collector peering

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.