Skip to main content

AS48610

OFORO

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Registry

Authoritative registration data

AS number
48610
Name
OFORO
Organisation
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS48610
176.97.194.0/24 IPv4 /24 not checked
2a13:8e40::/36 IPv6 /36 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 AS48610
Address families
CLOUD-IX MSK 10,000 Mbps IPv4 · IPv6
GNM-IX 10,000 Mbps IPv4 · IPv6
MSK-IX Moscow: MSK-IX peering network 10,000 Mbps IPv4 · IPv6
NetIX: NetIX IPv4 · IPv6
PITER-IX Frankfurt 10,000 Mbps IPv4
PITER-IX Helsinki 10,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 10,000 Mbps IPv4 · IPv6
PITER-IX Riga: RIX_PEERING_VLAN 10,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 10,000 Mbps IPv4 · IPv6
PITER-IX Tallinn: TLL_PEERING VLAN 10,000 Mbps IPv4
W-IX: vlan800 10,000 Mbps IPv4 · IPv6
inet2: vlan888 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 AS48610 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

18 networks seen before AS48610 in AS paths

Observed upstreams
Families
AS50509 303 642
v4
AS28917 336 480
v4 v6
AS9002 RETN-AS 220 431
v4 v6
AS31500 181 381
v4 v6
AS20764 RASCOM-AS 168 228
v4 v6
AS8218 NEO-ASN 5 53
v4 v6
AS25091 IP-Max 9 34
v4 v6
AS202984 team-host 22 28
v4
AS57304 7 13
v4
AS39351 ESAB-AS 4 8
v4 v6
AS6663 3 7
v4 v6
AS9198 3 7
v4 v6
AS60171 3 7
v4 v6
AS9049 3 5
v4
AS15958 3 5
v4
AS42295 TBISS-AS 3 5
v4
AS137409 GSLNETWORKS-AS-AP 3 5
v4
AS56655 GIGAHOST 2 2
v6

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS48610 in AS paths

Observed downstreams
Families
AS210281 299 970
v4
AS57712 536 758
v4 v6

No rows match “”.

Showing of

Uncertain adjacencies

20 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 3 31
v4 v6
AS47692 3 14
v4 v6
AS3170 3 7
v4 v6
AS28910 3 7
v4 v6
AS36236 NETACTUATE 3 7
v4 v6
AS41327 FIBERTELECOM-AS 3 7
v4 v6
AS41722 3 7
v4 v6
AS49434 3 7
v4 v6
AS205112 PHILUNET 3 7
v4 v6
AS209823 3 7
v4 v6
AS29049 3 5
v4
AS37721 ORG-VTS1-AFRINIC 3 5
v4
AS44901 3 5
v4
AS49673 TRUENETWORK 3 5
v4
AS51185 MAINSTREAMING-AS 3 5
v4
AS200612 3 5
v4
AS208972 3 5
v4
AS13004 2 4
v4
AS35598 3 3
v4
AS199524 GCORE 3 3
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.