Skip to main content

AS44863

STARNET-AS

STARNET TC LLC

Registry

Authoritative registration data

AS number
44863
Name
STARNET-AS
Organisation
STARNET TC LLC
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

0

Total announced

5

Announced prefixes

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

Prefixes announced by AS44863
185.93.185.0/24 IPv4 /24 not checked
185.93.187.0/24 IPv4 /24 not checked
193.138.245.0/24 IPv4 /24 not checked
193.138.246.0/24 IPv4 /24 not checked
193.138.247.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 AS44863
Address families
DTEL-IX: PUBLIC 10,000 Mbps IPv4
Filanco-IX 20,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 AS44863 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS44863 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 573 2,569
v4
AS1820 136 432
v4
AS28917 Fiord-AS 57 198
v4
AS3303 SWISSCOM 3 12
v4

No rows match “”.

Showing of

Observed downstreams

3 networks seen after AS44863 in AS paths

Observed downstreams
Families
AS33927 UKRMIRCOM-AS 233 987
v4
AS210069 187 239
v4
AS34323 65 74
v4

No rows match “”.

Showing of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 2 16
v4
AS48919 2 8
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.