Skip to main content

AS27008

BDC

BendTel

Registry

Authoritative registration data

AS number
27008
Name
BDC
Organisation
BendTel
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS27008
66.39.160.0/19 IPv4 /19 not checked
2607:fda0::/32 IPv6 /32 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 AS27008
Address families
Central Oregon Internet Exchange 10,000 Mbps IPv4 · IPv6
NWAX: Primary Peering VLAN 10,000 Mbps IPv4 · IPv6
SIX Seattle: MTU 1500 10,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 AS27008 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS27008 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 1,034 3,704
v4 v6
AS6461 ZAYO-6461 214 1,335
v4 v6
AS2914 NTT-DATA-2914 65 232
v4 v6
AS9002 RETN-AS 5 23
v4 v6
AS137409 GSLNETWORKS-AS-AP 5 20
v4
AS394256 CLOUDSINGULARITY 4 16
v4 v6

No rows match “”.

Showing of

Observed downstreams

3 networks seen after AS27008 in AS paths

Observed downstreams
Families
AS11080 461 2,648
v4 v6
AS6653 VERO-NETWORKS-AS6653 261 1,401
v4
AS35929 296 662
v4 v6

No rows match “”.

Showing of

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 4 48
v4 v6
AS49544 i3Dnet 4 32
v4 v6
AS36236 NETACTUATE 4 16
v4 v6
AS18106 VIEWQWEST-SG-AP 4 13
v4
AS35280 F5 4 13
v4
AS1828 UNITAS 3 3
v6
AS34927 iFog-GmbH 1 1
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.