Skip to main content

AS197184

Orbital-AS

Orbital Ltd

Registry

Authoritative registration data

AS number
197184
Name
Orbital-AS
Organisation
Orbital Ltd
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

0

Total announced

6

Announced prefixes

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

Prefixes announced by AS197184
85.14.52.0/22 IPv4 /22 not checked
85.14.8.0/22 IPv4 /22 not checked
82.119.88.0/23 IPv4 /23 not checked
88.203.248.0/24 IPv4 /24 not checked
88.203.249.0/24 IPv4 /24 not checked
89.252.222.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 AS197184
Address families
B-IX 1,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 AS197184 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS197184 in AS paths

Observed upstreams
Families
AS8262 215 1,108
v4
AS8717 240 840
v4
AS6939 HURRICANE 22 118
v4
AS59900 Balkan-Internet-Exchange 5 14
v4
AS57344 3 14
v4
AS15958 1 6
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS197184 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS13004 1 6
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.