Skip to main content

AS213782

GOFORCEX-AS

GoForceX Networks

Registry

Authoritative registration data

AS number
213782
Name
GOFORCEX-AS
Organisation
GoForceX Networks
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

3

Total announced

3

Announced prefixes

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

Prefixes announced by AS213782
2a14:67c1:70::/48 IPv6 /48 not checked
2a14:67c1:74::/48 IPv6 /48 not checked
2a14:67c1:75::/48 IPv6 /48 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 AS213782
Address families
BGP.Exchange - Tokyo 1,000 Mbps IPv6
FogIXP 100 Mbps IPv6
HN Internet Exchange (Main) 10,000 Mbps IPv6
ONIX 1,000 Mbps IPv4 · IPv6
ZXIX Hong Kong 1,000 Mbps 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 AS213782 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS213782 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 232 676
v6
AS44324 MOEDOVE-AS 247 345
v6
AS52025 PARADOXNETWORKS-LIMITED 9 31
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS213782 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
AS7721 1 2
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.