Skip to main content

AS207168

BUSINESS-TRADE-AS

Business Trade Ltd

Registry

Authoritative registration data

AS number
207168
Name
BUSINESS-TRADE-AS
Organisation
Business Trade Ltd
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 AS207168
85.142.180.0/22 IPv4 /22 not checked
77.91.98.0/23 IPv4 /23 not checked
178.236.139.0/24 IPv4 /24 not checked
212.192.47.0/24 IPv4 /24 not checked
77.91.125.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

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

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS207168 in AS paths

Observed upstreams
Families
AS12389 ROSTELECOM-AS 82 396
v4
AS31500 GNM-AS 63 276
v4
AS35598 INETCOM 120 147
v4
AS62255 BEMYLINK 44 50
v4
AS47692 NESSUS 2 16
v4
AS25091 IP-Max 3 12
v4
AS6204 ZET-NET 1 4
v4
AS6663 TTI-NET 1 4
v4
AS39351 ESAB-AS 1 4
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS207168 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

9 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.