Skip to main content

AS47680

NHCS

EOBO Ltd T/A BBnet

Registry

Authoritative registration data

AS number
47680
Name
NHCS
Organisation
EOBO Ltd T/A BBnet
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS47680
88.87.160.0/19 IPv4 /19 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 AS47680
Address families
INEX Cork: Peering LAN 10,000 Mbps IPv4
INEX LAN1: INEX LAN1 10,000 Mbps IPv4
INEX LAN2 10,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 AS47680 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS47680 in AS paths

Observed upstreams
Families
AS47720 CIX-AS 282 633
v4
AS174 COGENT-174 180 324
v4
AS6939 HURRICANE 35 55
v4
AS3303 SWISSCOM 19 38
v4
AS56911 ASN-WARIAN 4 6
v4
AS4455 BSO 2 3
v4
AS6204 2 3
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS47680 in AS paths

Observed downstreams
Families
AS197957 266 716
v4

No rows match “”.

Showing – of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS12969 Vodafone_Iceland 2 3
v4
AS13237 LAMBDANET-AS 2 3
v4
AS36236 NETACTUATE 2 3
v4
AS39122 BLACKNIGHT-AS 2 3
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.