Skip to main content

AS142281

YUUTA-BACKBONE

Yuuta Backbone

Registry

Authoritative registration data

AS number
142281
Name
YUUTA-BACKBONE
Organisation
Yuuta Backbone
Country
Flag of Canada CA Canada
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

2

Total announced

3

Announced prefixes

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

Prefixes announced by AS142281
44.30.150.0/24 IPv4 /24 not checked
2404:f4c0:f9c3::/48 IPv6 /48 not checked
2a0d:2580:8001::/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 AS142281
Address families
EVIX: Peering LAN 2,000 Mbps IPv6
Poema IX 500 Mbps IPv6
UNM-Exch Canada-West: Main 1,000 Mbps IPv4 · 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 AS142281 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS142281 in AS paths

Observed upstreams
Families
AS20473 388 1,006
v4 v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS142281 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS203472 POEMA-AS-EU 1 2
v6
AS207705 JK-NETWORK 1 1
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.