Datacamp/CDN77 (AS60068) do not announce 94.140.14.14 (AS212772) to BT (AS5400)

[ardel]

Issue Details

Currently BT customers are routed to your Amsterdam location via AS1299.

The optimum solution to achieve routing to your UK location would be for Datacamp to announce 94.140.14.0/24 to BT (AS5400) directly.

The current BGP sessions from https://lg.bt.net/ are below:

94.140.14.0/24	   *[BGP/170] 22w4d 01:07:10, MED 0, localpref 180
		      AS path: 1299 60068 212772 I, validation-state: valid
		    >  to 213.248.71.146 via ae7.0
		    [BGP/170] 19w0d 19:34:03, MED 0, localpref 180, from 166.49.205.250
		      AS path: 1299 60068 212772 I, validation-state: valid
		       to 166.49.195.45 via et-5/1/2.0
		       to 166.49.195.182 via et-5/1/5.0
		    >  to 166.49.195.111 via et-4/1/2.0
		    [BGP/170] 3w3d 17:08:43, MED 0, localpref 180, from 166.49.166.45
		      AS path: 1299 60068 212772 I, validation-state: valid
		       to 166.49.164.119 via et-2/0/2.0
		       to 166.49.164.111 via et-2/0/5.0
		    >  to 166.49.164.115 via et-2/1/2.0
		    [BGP/170] 1w4d 13:44:26, MED 0, localpref 180, from 166.49.166.61
		      AS path: 1299 60068 212772 I, validation-state: valid
		       to 166.49.195.193 via et-8/0/5.0
		       to 166.49.195.125 via et-4/0/2.0
		    >  to 166.49.195.127 via et-4/0/5.0
		    [BGP/170] 2w0d 13:32:27, MED 0, localpref 180, from 166.49.166.161
		      AS path: 1299 60068 212772 I, validation-state: valid
		       to 166.49.164.119 via et-2/0/2.0
		       to 166.49.164.111 via et-2/0/5.0
		    >  to 166.49.164.115 via et-2/1/2.0
		    [BGP/170] 2d 11:12:40, MED 0, localpref 180
		      AS path: 174 60068 212772 I, validation-state: valid
		    >  to 130.117.14.65 via et-3/0/5.0
		    [BGP/170] 13w6d 16:06:52, MED 0, localpref 180, from 166.49.166.60
		      AS path: 174 60068 212772 I, validation-state: valid
		       to 166.49.195.193 via et-8/0/5.0
		       to 166.49.195.125 via et-4/0/2.0
		    >  to 166.49.195.127 via et-4/0/5.0
		    [BGP/170] 15w3d 12:59:08, MED 0, localpref 180
		      AS path: 6453 60068 212772 I, validation-state: valid
		    >  to 195.219.83.104 via ae9.0
		    [BGP/170] 17:55:47, MED 0, localpref 180, from 166.49.166.216
		      AS path: 3491 60068 212772 I, validation-state: valid
		       to 166.49.164.121 via et-2/0/2.1
		       to 166.49.164.113 via et-2/0/5.1
		    >  to 166.49.164.117 via et-2/1/2.1
		    [BGP/170] 1w0d 20:45:52, MED 0, localpref 180, from 166.49.166.230
		      AS path: 3491 60068 212772 I, validation-state: valid
		       to 166.49.208.92 via ae12.0
		       to 166.49.195.45 via et-5/1/2.0
		       to 166.49.195.182 via et-5/1/5.0
		    >  to 166.49.195.111 via et-4/1/2.0
		    [BGP/170] 5w5d 03:31:46, MED 0, localpref 180, from 166.49.166.44
		      AS path: 3257 60068 212772 I, validation-state: valid
		       to 166.49.164.119 via et-2/0/2.0
		       to 166.49.164.111 via et-2/0/5.0
		    >  to 166.49.164.115 via et-2/1/2.0
		    [BGP/170] 11:50:32, MED 0, localpref 180, from 166.49.166.118
		      AS path: 33891 60068 212772 I, validation-state: valid
		    >  to 166.49.195.215 via et-9/0/0.0
		    [BGP/170] 11:50:31, MED 0, localpref 180, from 166.49.205.100
		      AS path: 33891 60068 212772 I, validation-state: valid
		       to 166.49.195.193 via et-8/0/5.0
		       to 166.49.195.125 via et-4/0/2.0
		    >  to 166.49.195.127 via et-4/0/5.0
		    [BGP/170] 16:48:27, MED 0, localpref 180, from 166.49.166.162
		      AS path: 33891 60068 212772 I, validation-state: valid
		       to 166.49.195.193 via et-8/0/5.0
		       to 166.49.195.125 via et-4/0/2.0
		    >  to 166.49.195.127 via et-4/0/5.0
		    [BGP/170] 2w2d 14:13:55, MED 0, localpref 180, from 166.49.205.16
		      AS path: 33891 60068 212772 I, validation-state: valid
		       to 166.49.195.193 via et-8/0/5.0
		       to 166.49.195.125 via et-4/0/2.0
		    >  to 166.49.195.127 via et-4/0/5.0
		    [BGP/170] 2w2d 14:13:55, MED 0, localpref 180, from 166.49.166.168
		      AS path: 33891 60068 212772 I, validation-state: valid
		       to 166.49.195.193 via et-8/0/5.0
		       to 166.49.195.125 via et-4/0/2.0
		    >  to 166.49.195.127 via et-4/0/5.0
		    [BGP/170] 05:31:49, MED 0, localpref 180, from 166.49.166.197
		      AS path: 33891 60068 212772 I, validation-state: valid
		       to 166.49.195.193 via et-8/0/5.0
		       to 166.49.195.125 via et-4/0/2.0
		    >  to 166.49.195.127 via et-4/0/5.0
		    [BGP/170] 2w2d 06:34:33, MED 0, localpref 180, from 166.49.205.101
		      AS path: 12956 60068 212772 I, validation-state: valid
		       to 166.49.195.193 via et-8/0/5.0
		       to 166.49.195.125 via et-4/0/2.0
		    >  to 166.49.195.127 via et-4/0/5.0
		    [BGP/170] 2d 21:12:50, MED 0, localpref 180, from 166.49.166.47
		      AS path: 6830 60068 212772 I, validation-state: valid
		       to 166.49.164.119 via et-2/0/2.0
		       to 166.49.164.111 via et-2/0/5.0
		       to 166.49.164.115 via et-2/1/2.0
		       to 166.49.195.45 via et-5/1/2.0
		    >  to 166.49.195.182 via et-5/1/5.0
		       to 166.49.195.111 via et-4/1/2.0
		    [BGP/170] 1w2d 08:23:56, MED 0, localpref 180, from 166.49.166.231
		      AS path: 7922 60068 212772 I, validation-state: valid
		    >  to 166.49.208.92 via ae12.0

Proposed solution

Contact Datacamp to check whether they can announce 94.140.14.0/24 to BT

Alternative solution

No response