Skip to main content

AS44884

DN-ROS-AS

Regional Online Systems Ltd.

Registry

Authoritative registration data

AS number
44884
Name
DN-ROS-AS
Organisation
Regional Online Systems Ltd.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS44884
176.103.208.0/22 IPv4 /22 not checked
195.216.210.0/23 IPv4 /23 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS44884 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS44884 in AS paths

Observed upstreams
Families
AS12773 MM-AS 321 403
v4
AS201776 MIRANDA-AS 200 255
v4
AS8218 NEO-ASN 5 24
v4
AS47692 NESSUS 2 8
v4
AS6204 ZET-NET 1 2
v4
AS6663 TTI-NET 1 2
v4
AS9198 KAZTELECOM-AS 1 2
v4
AS15958 CETIN_doo_AS 1 2
v4
AS60171 AFRIX-AS 1 2
v4
AS62000 AS62000 1 2
v4
AS8447 A1TELEKOM-AT 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS44884 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

12 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 12
v4
AS3170 VELOXSERV 1 2
v4
AS13004 SOX 1 2
v4
AS37721 ORG-VTS1-AFRINIC 1 2
v4
AS41327 FIBERTELECOM-AS 1 2
v4
AS44901 belcloud 1 2
v4
AS49434 FBWNETWORKS 1 2
v4
AS49673 TRUENETWORK 1 2
v4
AS51185 MAINSTREAMING-AS 1 2
v4
AS200612 GulfBridgeInternational 1 2
v4
AS205112 PHILUNET 1 2
v4
AS208972 1 2
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.