Skip to main content

AS2818

BBC

BBC Internet Services, UK

Registry

Authoritative registration data

AS number
2818
Name
BBC
Organisation
BBC Internet Services, UK
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

3

Total announced

7

Announced prefixes

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

Prefixes announced by AS2818
132.185.0.0/16 IPv4 /16 not checked
212.58.224.0/19 IPv4 /19 not checked
132.185.112.0/20 IPv4 /20 not checked
132.185.128.0/20 IPv4 /20 not checked
2001:41c0::/32 IPv6 /32 not checked
2001:41c1::/32 IPv6 /32 not checked
2001:41c2::/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 AS2818
Address families
LINX LON1: Main 400,000 Mbps IPv4 · IPv6
LINX LON2 80,000 Mbps IPv4 · IPv6
LINX Manchester 100,000 Mbps IPv4 · IPv6
LINX Scotland: LINX Scotland 10,000 Mbps IPv4 · IPv6
LONAP: LON0 200,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 AS2818 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

50 networks seen before AS2818 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS2818 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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