Get Help & Support

Support and Resources

Report a bug or feature request

If you think you may have found a bug, or if you have a feature request that you would like to share with the Google Maps Platform team, please file a bug or feature request in our Issue Tracker.

If you are submitting a bug, please include a sample that demonstrates the problem to help us reproduce exactly what you are seeing.

All Issues per API Report a Bug Submit a Feature Request
Maps SDK for Unity Bug Report Feature Request
Playable Locations API Bug Report Feature Request
Issue tracker status codes
New This issue/feature request has not been triaged.
Assigned The issue has a person assigned to it.
Accepted The issue has been acknowledged by the assignee, who will provide updates when active investigations begin.
Fixed The issue is resolved in a released version.
Fixed (Verified) The issue has been addressed and the correctness of the fix has been confirmed.
Won't fix (Not reproducible) There is either not enough information to fix the issue, or the issue as reported cannot be re-created.
Won't fix (Intended behavior) The issue describes the expected behavior of the product under the reported circumstances.
Won't fix (Obsolete) The issue is no longer relevant due to changes in the product.
Won't fix (Infeasible) The issue requires changes that cannot be implemented in the foreseeable future.
Duplicate This report duplicates an existing issue.
Issue tracker triaged codes
PendingFurtherReview This issue has passed initial triage and is waiting for priority review.
NeatIdea Feature request is acknowledged. We are currently evaluating this request but do not have any plans to implement it. Please star to vote and comment to discuss your use case.
NeedsMoreInfo This issue/feature request requires more information from the reporter.

Contacting the support team

Creating a support case

Project Owners, Project Editors, and Tech Support Editors can create support cases. If you don’t have one of these roles, contact your Project Owner or Organization Admin to get access.

  1. Visit the Google Maps Platform Support page in the Cloud Console.
  2. Select the project related to your question, in the top dropdown bar of the Cloud Console.
    • To file a technical support case, you must have a Project Owner, Project Editor, or Tech Support Editor role.
    • To file a billing support case, you must have a Project Owner or Project Editor role.
  3. Fill out the fields in detail on the Create a new support case section. It may take a minute to create your case.

Granting support access

A Project Owner or an Organization Admin can grant all available roles from the IAM page.

  1. Open the IAM page in the Cloud Console.
  2. Select Select a project > choose a project from the dropdown > Open.
  3. Select Add, then enter the new member’s email address.
    • You can add individuals, service accounts, or Google Groups as members, but every project must have at least one individual as a member.
  4. Select the member’s role. For best security practices, we strongly recommend giving the member the lowest permissions needed. Members with Project Owner permissions are able to manage all aspects of the project, including shutting it down.
    • To grant Project Owner or Project Editor permissions, choose the appropriate role under Project.
    • To limit a member’s permissions to filing technical support cases, choose the Tech Support Editor role under Support.
  5. Save your changes.

Escalating a case

If you think that your case is not being handled optimally, you can escalate the case. An escalation manager will review your case and make sure it is handled properly.

Note: Escalation managers can provide additional expertise or better prioritize a case based on business requirements. They cannot grant exceptions to policies or terms of service.

One hour after a case is first submitted, you may escalate it. Use the Escalate button found in the footer of your support emails, in the case creation confirmation email, or in any response to the case.

Support response times

Support response times are indicated in the table below (resolution times may vary):

Severity level Definition Response time
Critical Impact - Service Unusable in Production Critical functions of your production application aren't available with no workaround. 1 hour on weekdays, excluding regional holidays
High Impact - Service Severely Impaired This issue is critically impacting a single user or critically impacting collaboration among users. Service does not work as expected, with no feasible workaround. 24 hours on weekdays
Medium Impact - Service Partially Impaired Service does not work as expected but a workaround is easily available. 24 hours on weekdays
Low Impact - Service Fully Usable Service does not work as desired, but functions (a workaround is not necessary). 24 hours on weekdays

Privacy inquiries

For questions related to data privacy and protection, you can contact us using the Data Privacy Inquiry Form.

Staying informed

Here are some other ways to stay up to date with the Google Maps Platform:

  • Subscribe to our Google Groups to stay up to date with changes, outages, and other announcements.
  • Google Maps Platform Blog: A useful source of news and updates across all of Google's Geo developer products.
  • Google Cloud Blog: Provides updates on all Google Cloud products, including the Google Maps Platform.

Google frequently interacts with the developer community through screencasts and YouTube shows.

Terms of use

For your reference, here are the documents relating to your usage:

  • Terms of Service: Describes your rights and obligations as a Google Maps Platform customer.