US4 API is Good

5:27am May 29, 2017 -0400

## Response Times

City | Average Load Time | Last Load Time | Last Recorded |
---|---|---|---|

Akron, OH | 0.2 seconds | 0.29 seconds | |

Albuquerque, NM | 0.26 seconds | 0.21 seconds | |

Amsterdam, Netherlands | 0.25 seconds | 0.2 seconds | |

Annapolis, MD | 0.26 seconds | 0.11 seconds | |

Atlanta, GA | 0.13 seconds | 0.14 seconds | |

Auckland, New Zealand | 0.4 seconds | 0.4 seconds | |

Bedford, NH | 0.12 seconds | 0.12 seconds | |

Boise, ID | 0.19 seconds | 0.4 seconds | |

Boston, MA | 0.26 seconds | 0.28 seconds | |

Brisbane, Australia | 0.47 seconds | 0.34 seconds | |

Brussels, Belgium | 0.22 seconds | 0.13 seconds | |

Bucharest, Romania | 0.45 seconds | 0.39 seconds | |

Buenos Aires, Argentina | 0.58 seconds | 0.47 seconds | |

Calgary, Canada | 0.27 seconds | 0.21 seconds | |

Charlotte, NC | 0.17 seconds | 0.21 seconds | |

Chicago, IL | 0.26 seconds | 0.16 seconds | |

Cleveland, OH | 0.17 seconds | 0.16 seconds | |

Columbus, OH | 0.17 seconds | 0.12 seconds | |

Copenhagen, Denmark | 0.19 seconds | 0.12 seconds | |

Dallas, TX | 0.2 seconds | 0.32 seconds | |

Denver, CO | 0.19 seconds | 0.24 seconds | |

Dublin, Ireland | 0.35 seconds | 0.34 seconds | |

Halifax, Canada | 0.27 seconds | 0.21 seconds | |

Hamburg, Germany | 0.23 seconds | 0.29 seconds | |

Helsinki, Finland | 0.25 seconds | 0.24 seconds | |

Honolulu, HI | 0.45 seconds | 0.43 seconds | |

Kansas City, MO | 0.17 seconds | 0.12 seconds | |

Las Vegas, NV | 0.28 seconds | 0.36 seconds | |

Lisbon, Portugal | 0.24 seconds | 0.06 seconds | |

London, England | 0.21 seconds | 0.2 seconds | |

Los Angeles, CA | 0.41 seconds | 0.33 seconds | |

Madrid, Spain | 0.25 seconds | 0.25 seconds | |

Manchester, England | 0.2 seconds | 0.17 seconds | |

Miami, FL | 0.24 seconds | 0.12 seconds | |

Milan, Italy | 0.26 seconds | 0.21 seconds | |

Milwaukee, WI | 0.17 seconds | 0.13 seconds | |

Minneapolis, MN | 0.2 seconds | 0.17 seconds | |

Montreal, Canada | 0.2 seconds | 0.12 seconds | |

Munich, Germany | 0.34 seconds | 0.37 seconds | |

Newark, NJ | 0.12 seconds | 0.12 seconds | |

New Orleans, LA | 0.24 seconds | 0.34 seconds | |

New York, NY | 0.09 seconds | 0.09 seconds | |

Omaha, NE | 0.18 seconds | 0.25 seconds | |

Oslo, Norway | 0.26 seconds | 0.21 seconds | |

Paris, France | 0.21 seconds | 0.14 seconds | |

Philadelphia, PA | 0.18 seconds | 0.08 seconds | |

Phoenix, AZ | 0.24 seconds | 0.23 seconds | |

Pittsburgh, PA | 0.19 seconds | 0.09 seconds | |

Portland, OR | 0.23 seconds | 0.18 seconds | |

Prague, Czech Republic | 0.29 seconds | 0.44 seconds | |

Raleigh, NC | 0.17 seconds | 0.1 seconds | |

San Diego, CA | 0.2 seconds | 0.15 seconds | |

San Francisco, CA | 0.22 seconds | 0.35 seconds | |

San Jose, CA | 0.22 seconds | 0.15 seconds | |

Seattle, WA | 0.23 seconds | 0.2 seconds | |

St. Louis, MO | 0.32 seconds | 0.18 seconds | |

Stockholm, Sweden | 0.38 seconds | 0.27 seconds | |

Taipei, Taiwan | 0.62 seconds | 0.53 seconds | |

Tampa, FL | 0.17 seconds | 0.25 seconds | |

Tokyo, Japan | 0.46 seconds | 0.67 seconds | |

Toronto, Canada | 0.37 seconds | 0.14 seconds | |

Vancouver, Canada | 0.25 seconds | 0.23 seconds | |

Warsaw, Poland | 0.33 seconds | 0.41 seconds | |

Washington, D.C. | 0.69 seconds | 0.09 seconds | |

Zurich, Switzerland | 0.21 seconds | 0.33 seconds |

### What do the numbers mean?

The API response time represents how long it took the monitoring servers to ping MailChimp's API v3.0.