bgpreport

Network · data from 2026-11-12

AS40015 Atlantic Metro (Yellow Fiber Networks)

Registry name: MOVECLICKLLC - Atlantic Metro Communications II, Inc., US · PeeringDB

8IPv4 routes 0.0% RPKI valid · 87.5% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
9No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS40015, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS40015, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

216.14.80.0/24 No ROA Nonecovered by 216.14.80.0/20 672 100% 66
67.23.96.0/19 No ROA Other IRR onlyALTDB, BBOI 673 100% 66
69.71.211.0/24 No ROA Other IRR onlyALTDB, BBOI 673 100% 66
69.71.221.0/24 No ROA Other IRR onlyALTDB, BBOI 673 100% 66
216.14.80.0/20 No ROA Other IRR onlyALTDB, BBOI 673 100% 66
216.177.152.0/24 No ROA Other IRR onlyALTDB, BBOI 673 100% 66
216.177.155.0/24 No ROA Other IRR onlyALTDB, BBOI 673 100% 66
216.177.157.0/24 No ROA Other IRR onlyALTDB, BBOI 673 100% 66
2607:fd50::/32 No ROA Other IRR onlyALTDB, BBOI 636 100% 67

AS-SET

AS40015's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 19 are in fix.csv.

  • ROA: none9
  • Route object: none1
  • Route object: RIR8
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none216.14.80.0/24No ROA covers it. Add a ROA for AS40015, maxLength 24.672 of 673
Route object: none216.14.80.0/24No route object for it. A route object for 216.14.80.0/20 with origin AS40015 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40015 in the RIR database for the space.672 of 673
ROA: none67.23.96.0/19No ROA covers it. Add a ROA for AS40015, maxLength 19.673 of 673
Route object: RIR67.23.96.0/19Route object only in ALTDB, BBOI. Add it in the RIR database for the space.673 of 673
ROA: none69.71.211.0/24No ROA covers it. Add a ROA for AS40015, maxLength 24.673 of 673
Route object: RIR69.71.211.0/24Route object only in ALTDB, BBOI. Add it in the RIR database for the space.673 of 673
ROA: none69.71.221.0/24No ROA covers it. Add a ROA for AS40015, maxLength 24.673 of 673
Route object: RIR69.71.221.0/24Route object only in ALTDB, BBOI. Add it in the RIR database for the space.673 of 673
ROA: none216.14.80.0/20No ROA covers it. Add a ROA for AS40015, maxLength 20.673 of 673
Route object: RIR216.14.80.0/20Route object only in ALTDB, BBOI. Add it in the RIR database for the space.673 of 673
ROA: none216.177.152.0/24No ROA covers it. Add a ROA for AS40015, maxLength 24.673 of 673
Route object: RIR216.177.152.0/24Route object only in ALTDB, BBOI. Add it in the RIR database for the space.673 of 673
ROA: none216.177.155.0/24No ROA covers it. Add a ROA for AS40015, maxLength 24.673 of 673
Route object: RIR216.177.155.0/24Route object only in ALTDB, BBOI. Add it in the RIR database for the space.673 of 673
ROA: none216.177.157.0/24No ROA covers it. Add a ROA for AS40015, maxLength 24.673 of 673
Route object: RIR216.177.157.0/24Route object only in ALTDB, BBOI. Add it in the RIR database for the space.673 of 673
ROA: none2607:fd50::/32No ROA covers it. Add a ROA for AS40015, maxLength 32.636 of 636
Route object: RIR2607:fd50::/32Route object only in ALTDB, BBOI. Add it in the RIR database for the space.636 of 636

Route objects not announced

Route objects with origin AS40015 whose prefix no peer sees AS40015 announce. Many are kept on purpose (backup routes, space announced only in some places).

2620:de:8000::/48ALTDB, BBOINo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.