The routing service can be used to find the best route to get from one location to another or to visit several locations. The best route can be the fastest route for a given time of day considering the traffic conditions applicable during that time. If you have more than two stops to visit, the routing service can determine the best order in which to visit the locations (the traveling salesman problem).
Required parameters:
stops - Specify two or more semicolon-delimited locations(Lat/Lng) between which the route is to be found. Max: 25.Optional parameters:
avoid_highways - The route should avoid highways.avoid_tolls - The route should avoid toll roads.avoid_ferries - The route should avoid ferries.avoid_highways - The route should avoid highways.geometry_format - The format of the returned route geometry: latlng or lnglat. Default: latlngoptimize - Instructs the API to reorder stops to find the optimized route. The route first stop and last stop order is not changed, their position is considered fixed.Required parameters:
origin - The location from which you wish to calculate directions.destination - The location to which you wish to calculate directions.Optional parameters:
avoid_highways - The route should avoid highways.avoid_tolls - The route should avoid toll roads.avoid_ferries - The route should avoid ferries.avoid_highways - The route should avoid highways.geometry_format - The format of the returned route geometry: latlng or lnglat. Default: latlngstart_time - Time when travel is expected to start. This time is used to take into account traffic conditions. You can specify the time as an integer in seconds since midnight, January 1, 1970 UTC or you can use “now” to specify the current time.The main difference between FindDrivingRoute and FindDrivingPath is that FindDrivingRoute is optimized for a route with multiple stops and can optimize the route (reorder stops) with parameter optimize=true. FindDrivingPath does not change the order of visiting points, but is optimized for a route between two points. Also FindDrivingPath can take traffic conditions into account.
The service returns a optimal route with detailed information:
A Route contains the following fields:
distance contains the length of route (meters).duration contains the time of route (seconds).geometry contains the geometry of route. By default, geometry contains a single coordinates object, which is a two-dimensional array of points (Latitude/Longitude).bounds contains the bounds of geometry.legs contains an array which contains information about a leg of the route, between two locations within the route. A route with no intermediate waypoints will contain exactly one leg within the legs array. Each leg consists of a series of steps.A Leg contains the following fields:
distance contains the length of leg (meters).duration contains the time of leg (seconds).start_point_index contains the index of point (within geometry.coordinates array) at which the leg starts.start_point contains the coordinate of point (within geometry.coordinates array) at which the leg starts.end_point_index contains the index of point (within geometry.coordinates array) at which the leg ends.end_point contains the coordinate of point (within geometry.coordinates array) at which the leg ends.bounds contains the bounds of leg geometry.steps contains an array which contains information about a step of the leg.A Step contains the following fields:
distance contains the length of step (meters).duration contains the time of step (seconds).start_point_index contains the index of point (within geometry.coordinates array) at which the step starts.start_point contains the coordinate of point (within geometry.coordinates array) at which the step starts.end_point_index contains the index of point (within geometry.coordinates array) at which the step ends.end_point contains the coordinate of point (within geometry.coordinates array) at which the step ends.bounds contains the bounds of step geometry.maneuver contains the action to take for the step (“turn left”, “turn right”, etc.).Please note that for FindDrivingPath, the route does not contain the field legs but directly contains the field steps.
Finding the optimal route for visiting multiple locations
FindDrivingRoute - Características del Endpoint
| Objeto | Descripción |
|---|---|
stops |
[Requerido] Specify two or more semicolon-delimited locations(Lat/Lng) between which the route is to be found. Max: 25. For Example: 40.629041,-74.025606;40.630099,-73.993521;40.644895,-74.013818;40.627177,-73.980853 |
optimize |
Opcional true for reorder stops to find the optimized route. The route first stop and last stop order is not changed, their position is considered fixed. |
avoid_ferries |
Opcional true for avoid ferries. Default: false |
avoid_highways |
Opcional true for avoid highways. Default: false |
avoid_tolls |
Opcional true for avoid toll roads. Default: false |
{
"route": {
"distance": 10148,
"duration": 2654,
"bounds": {
"south": 40.618996,
"west": -74.025801,
"north": 40.645331,
"east": -73.98078
},
"geometry": {
"coordinates": [
[
40.629103,
-74.025801
],
[
40.629409,
-74.025679
],
[
40.630117,
-74.025375
],
[
40.630245,
-74.025325
],
[
40.630726,
-74.025122
],
[
40.630804,
-74.025081
],
[
40.630814,
-74.02499
],
[
40.630804,
-74.024939
],
[
40.630794,
-74.024899
],
[
40.630785,
-74.024858
],
[
40.630726,
-74.024726
],
[
40.630677,
-74.024635
],
[
40.630667,
-74.024625
],
[
40.630402,
-74.024169
],
[
40.62996,
-74.023422
],
[
40.629901,
-74.023321
],
[
40.629773,
-74.02312
],
[
40.629695,
-74.02297
],
[
40.629478,
-74.02264
],
[
40.628726,
-74.021398
],
[
40.628057,
-74.020293
],
[
40.627946,
-74.020106
],
[
40.627876,
-74.020007
],
[
40.627755,
-74.01981
],
[
40.627624,
-74.019592
],
[
40.627493,
-74.019385
],
[
40.627432,
-74.019286
],
[
40.627382,
-74.019196
],
[
40.627271,
-74.019018
],
[
40.627068,
-74.01868
],
[
40.626977,
-74.01851
],
[
40.626967,
-74.0185
]
]
},
"legs": [
{
"distance": 3919,
"duration": 816,
"start_point_index": 0,
"start_point": {
"lat": 40.629103,
"lng": -74.025801
},
"end_point_index": 120,
"end_point": {
"lat": 40.630157,
"lng": -73.993608
},
"bounds": {
"south": 40.618996,
"west": -74.025801,
"north": 40.630814,
"east": -73.993608
},
"steps": [
{
"distance": 199,
"duration": 40,
"start_point_index": 0,
"start_point": {
"lat": 40.629103,
"lng": -74.025801
},
"end_point_index": 5,
"end_point": {
"lat": 40.630804,
"lng": -74.025081
},
"bounds": {
"south": 40.629103,
"west": -74.025801,
"north": 40.630804,
"east": -74.025081
}
},
{
"distance": 2137,
"duration": 367,
"start_point_index": 5,
"start_point": {
"lat": 40.630804,
"lng": -74.025081
},
"end_point_index": 77,
"end_point": {
"lat": 40.618996,
"lng": -74.005211
},
"bounds": {
"south": 40.618996,
"west": -74.025081,
"north": 40.630814,
"east": -74.005211
},
"maneuver": "turn right"
},
{
"distance": 1583,
"duration": 409,
"start_point_index": 77,
"start_point": {
"lat": 40.618996,
"lng": -74.005211
},
"end_point_index": 120,
"end_point": {
"lat": 40.630157,
"lng": -73.993608
},
"bounds": {
"south": 40.618996,
"west": -74.005211,
"north": 40.630157,
"east": -73.993608
},
"maneuver": "turn left"
}
]
},
{
"distance": 2600,
"duration": 747,
"start_point_index": 120,
"start_point": {
"lat": 40.630157,
"lng": -73.993608
},
"end_point_index": 155,
"end_point": {
"lat": 40.645027,
"lng": -74.01398
},
"bounds": {
"south": 40.630157,
"west": -74.015422,
"north": 40.645027,
"east": -73.993411
},
"steps": [
{
"distance": 27,
"duration": 6,
"start_point_index": 120,
"start_point": {
"lat": 40.630157,
"lng": -73.993608
},
"end_point_index": 121,
"end_point": {
"lat": 40.630343,
"lng": -73.993411
},
"bounds": {
"south": 40.630157,
"west": -73.993608,
"north": 40.630343,
"east": -73.993411
}
},
{
"distance": 2376,
"duration": 675,
"start_point_index": 121,
"start_point": {
"lat": 40.630343,
"lng": -73.993411
},
"end_point_index": 151,
"end_point": {
"lat": 40.643633,
"lng": -74.015422
},
"bounds": {
"south": 40.630343,
"west": -74.015422,
"north": 40.643633,
"east": -73.993411
},
"maneuver": "turn left"
},
{
"distance": 197,
"duration": 66,
"start_point_index": 151,
"start_point": {
"lat": 40.643633,
"lng": -74.015422
},
"end_point_index": 155,
"end_point": {
"lat": 40.645027,
"lng": -74.01398
},
"bounds": {
"south": 40.643633,
"west": -74.015422,
"north": 40.645027,
"east": -74.01398
},
"maneuver": "turn right"
}
]
},
{
"distance": 3629,
"duration": 1091,
"start_point_index": 155,
"start_point": {
"lat": 40.645027,
"lng": -74.01398
},
"end_point_index": 210,
"end_point": {
"lat": 40.627281,
"lng": -73.98078
},
"bounds": {
"south": 40.627281,
"west": -74.01398,
"north": 40.645331,
"east": -73.98078
},
"steps": [
{
"distance": 43,
"duration": 9,
"start_point_index": 155,
"start_point": {
"lat": 40.645027,
"lng": -74.01398
},
"end_point_index": 156,
"end_point": {
"lat": 40.645331,
"lng": -74.01366
},
"bounds": {
"south": 40.645027,
"west": -74.01398,
"north": 40.645331,
"east": -74.01366
}
},
{
"distance": 3117,
"duration": 933,
"start_point_index": 156,
"start_point": {
"lat": 40.645331,
"lng": -74.01366
},
"end_point_index": 202,
"end_point": {
"lat": 40.627896,
"lng": -73.984796
},
"bounds": {
"south": 40.627896,
"west": -74.01366,
"north": 40.645331,
"east": -73.984796
},
"maneuver": "turn right"
},
{
"distance": 158,
"duration": 58,
"start_point_index": 202,
"start_point": {
"lat": 40.627896,
"lng": -73.984796
},
"end_point_index": 204,
"end_point": {
"lat": 40.629023,
"lng": -73.983661
},
"bounds": {
"south": 40.627896,
"west": -73.984796,
"north": 40.629023,
"east": -73.983661
},
"maneuver": "turn left"
},
{
"distance": 311,
"duration": 91,
"start_point_index": 204,
"start_point": {
"lat": 40.629023,
"lng": -73.983661
},
"end_point_index": 210,
"end_point": {
"lat": 40.627281,
"lng": -73.98078
},
"bounds": {
"south": 40.627281,
"west": -73.983661,
"north": 40.629023,
"east": -73.98078
},
"maneuver": "turn right"
}
]
}
]
}
}
curl --location --request GET 'https://zylalabs.com/api/3932/trueway+routing+api/4659/finddrivingroute?stops=40.629041,-74.025606;40.630099,-73.993521;40.644895,-74.013818;40.627177,-73.980853' --header 'Authorization: Bearer YOUR_API_KEY'
Finding the best route between an origin and a destination
FindDrivingPath - Características del Endpoint
| Objeto | Descripción |
|---|---|
origin |
[Requerido] The location from which you wish to calculate directions. For Example: 40.629041,-74.025606 |
destination |
[Requerido] The location to which you wish to calculate directions. For Example: 40.627177,-73.980853 |
start_time |
Opcional Time when travel is expected to start. You can specify the time as an integer in seconds since midnight, January 1, 1970 UTC or you can use "now" to specify the current time. |
avoid_ferries |
Opcional true for avoid ferries. Default: false |
avoid_highways |
Opcional true for avoid highways. Default: false |
avoid_tolls |
Opcional true for avoid toll roads. Default: false |
{
"route": {
"distance": 5395,
"duration": 1094,
"bounds": {
"south": 40.620537,
"west": -74.025801,
"north": 40.630814,
"east": -73.98078
},
"geometry": {
"coordinates": [
[
40.629103,
-74.025801
],
[
40.629409,
-74.025679
],
[
40.630117,
-74.025375
],
[
40.630245,
-74.025325
],
[
40.630726,
-74.025122
],
[
40.630804,
-74.025081
],
[
40.630814,
-74.02499
],
[
40.630804,
-74.024939
],
[
40.630794,
-74.024899
],
[
40.630785,
-74.024858
],
[
40.630726,
-74.024726
],
[
40.630677,
-74.024635
],
[
40.630667,
-74.024625
],
[
40.630402,
-74.024169
],
[
40.62996,
-74.023422
],
[
40.629901,
-74.023321
],
[
40.629773,
-74.02312
],
[
40.629695,
-74.02297
],
[
40.629478,
-74.02264
],
[
40.628726,
-74.021398
],
[
40.628057,
-74.020293
],
[
40.627946,
-74.020106
],
[
40.627876,
-74.020007
],
[
40.627755,
-74.01981
],
[
40.627624,
-74.019592
],
[
40.627493,
-74.019385
],
[
40.627432,
-74.019286
],
[
40.627382,
-74.019196
],
[
40.627271,
-74.019018
],
[
40.627068,
-74.01868
],
[
40.626977,
-74.01851
]
]
},
"steps": [
{
"distance": 199,
"duration": 40,
"start_point_index": 0,
"start_point": {
"lat": 40.629103,
"lng": -74.025801
},
"end_point_index": 5,
"end_point": {
"lat": 40.630804,
"lng": -74.025081
},
"bounds": {
"south": 40.629103,
"west": -74.025801,
"north": 40.630804,
"east": -74.025081
}
},
{
"distance": 1661,
"duration": 285,
"start_point_index": 5,
"start_point": {
"lat": 40.630804,
"lng": -74.025081
},
"end_point_index": 68,
"end_point": {
"lat": 40.621637,
"lng": -74.00964
},
"bounds": {
"south": 40.621637,
"west": -74.025081,
"north": 40.630814,
"east": -74.00964
},
"maneuver": "turn right"
},
{
"distance": 808,
"duration": 173,
"start_point_index": 68,
"start_point": {
"lat": 40.621637,
"lng": -74.00964
},
"end_point_index": 85,
"end_point": {
"lat": 40.627331,
"lng": -74.003705
},
"bounds": {
"south": 40.621637,
"west": -74.00964,
"north": 40.627331,
"east": -74.003705
},
"maneuver": "turn left"
},
{
"distance": 1213,
"duration": 211,
"start_point_index": 85,
"start_point": {
"lat": 40.627331,
"lng": -74.003705
},
"end_point_index": 107,
"end_point": {
"lat": 40.620537,
"lng": -73.992483
},
"bounds": {
"south": 40.620537,
"west": -74.003705,
"north": 40.627331,
"east": -73.992483
},
"maneuver": "turn right"
},
{
"distance": 1203,
"duration": 294,
"start_point_index": 107,
"start_point": {
"lat": 40.620537,
"lng": -73.992483
},
"end_point_index": 132,
"end_point": {
"lat": 40.629023,
"lng": -73.983661
},
"bounds": {
"south": 40.620537,
"west": -73.992483,
"north": 40.629023,
"east": -73.983661
},
"maneuver": "turn left"
},
{
"distance": 311,
"duration": 91,
"start_point_index": 132,
"start_point": {
"lat": 40.629023,
"lng": -73.983661
},
"end_point_index": 138,
"end_point": {
"lat": 40.627281,
"lng": -73.98078
},
"bounds": {
"south": 40.627281,
"west": -73.983661,
"north": 40.629023,
"east": -73.98078
},
"maneuver": "turn right"
}
]
}
}
curl --location --request GET 'https://zylalabs.com/api/3932/trueway+routing+api/4660/finddrivingpath?origin=40.629041,-74.025606&destination=40.627177,-73.980853' --header 'Authorization: Bearer YOUR_API_KEY'
| Encabezado | Descripción |
|---|---|
Autorización
|
[Requerido] Debería ser Bearer access_key. Consulta "Tu Clave de Acceso a la API" arriba cuando estés suscrito. |
Sin compromiso a largo plazo. Mejora, reduce o cancela en cualquier momento. La Prueba Gratuita incluye hasta 50 solicitudes.
Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.
Prices are listed in USD. We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble with paying by card, just contact us at [email protected]
Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further
Prices are based on a recurring monthly subscription depending on the plan selected — plus overage fees applied when a developer exceeds a plan’s quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.
Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.
You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]
Both endpoints return detailed routing information, including distance, duration, route geometry, bounds, and turn-by-turn directions. The FindDrivingRoute endpoint also provides optimized routes for multiple stops, while FindDrivingPath focuses on routes between two specific locations.
Key fields include "distance" (length of the route in meters), "duration" (time in seconds), "geometry" (coordinates of the route), "bounds" (geographical limits), and "legs" or "steps" (detailed route segments).
Parameters include "stops" for FindDrivingRoute, and "origin" and "destination" for FindDrivingPath. Optional parameters include "avoid_highways," "avoid_tolls," "avoid_ferries," "geometry_format," and "start_time" for traffic considerations.
The response is structured with a "route" object containing distance, duration, geometry, and bounds. For FindDrivingRoute, it includes "legs" for multi-stop routes, while FindDrivingPath directly lists "steps" for two-point routes.
Typical use cases include navigation apps, logistics planning, and travel itinerary optimization. Users can find the fastest routes, avoid specific road types, or plan multi-stop trips efficiently.
Data accuracy is maintained through the integration of historical and live traffic conditions, ensuring that routes reflect current traffic patterns. Regular updates and quality checks enhance the reliability of the routing information.
Users can customize requests by specifying parameters such as "avoid_highways" or "optimize" to reorder stops. This allows for tailored routing based on user preferences and travel needs.
"Distance" indicates the total length of the route, "duration" shows the estimated travel time, "geometry" provides the route's coordinates, and "steps" detail individual actions required to navigate the route.
Zyla API Hub es como una gran tienda de APIs, donde puedes encontrar miles de ellas en un solo lugar. También ofrecemos soporte dedicado y monitoreo en tiempo real de todas las APIs. Una vez que te registres, puedes elegir qué APIs quieres usar. Solo recuerda que cada API necesita su propia suscripción. Pero si te suscribes a varias, usarás la misma clave para todas, lo que hace todo más fácil para ti.
Los precios se muestran en USD (dólar estadounidense), EUR (euro), CAD (dólar canadiense), AUD (dólar australiano) y GBP (libra esterlina). Aceptamos todas las principales tarjetas de débito y crédito. Nuestro sistema de pago utiliza la última tecnología de seguridad y está respaldado por Stripe, una de las compañías de pago más confiables del mundo. Si tienes algún problema para pagar con tarjeta, contáctanos en [email protected]
Además, si ya tienes una suscripción activa en cualquiera de estas monedas (USD, EUR, CAD, AUD, GBP), esa moneda se mantendrá para suscripciones posteriores. Puedes cambiar la moneda en cualquier momento siempre que no tengas suscripciones activas.
La moneda local que aparece en la página de precios se basa en el país de tu dirección IP y se proporciona solo como referencia. Los precios reales están en USD (dólar estadounidense). Cuando realices un pago, el cargo aparecerá en tu estado de cuenta en USD, incluso si ves el monto equivalente en tu moneda local en nuestro sitio web. Esto significa que no puedes pagar directamente en tu moneda local.
Ocasionalmente, un banco puede rechazar el cargo debido a sus configuraciones de protección contra fraude. Te sugerimos comunicarte con tu banco primero para verificar si están bloqueando nuestros cargos. También puedes acceder al Portal de Facturación y cambiar la tarjeta asociada para realizar el pago. Si esto no funciona y necesitas más ayuda, por favor contacta a nuestro equipo en [email protected]
Los precios se determinan mediante una suscripción recurrente mensual o anual, dependiendo del plan elegido.
Las llamadas a la API se descuentan de tu plan en base a solicitudes exitosas. Cada plan incluye una cantidad específica de llamadas que puedes realizar por mes. Solo las llamadas exitosas, indicadas por una respuesta con estado 200, se contarán en tu total. Esto asegura que las solicitudes fallidas o incompletas no afecten tu cuota mensual.
Zyla API Hub funciona con un sistema de suscripción mensual recurrente. Tu ciclo de facturación comenzará el día en que compres uno de los planes de pago, y se renovará el mismo día del mes siguiente. Así que recuerda cancelar tu suscripción antes si quieres evitar futuros cargos.
Para actualizar tu plan de suscripción actual, simplemente ve a la página de precios de la API y selecciona el plan al que deseas actualizarte. La actualización será instantánea, permitiéndote disfrutar inmediatamente de las funciones del nuevo plan. Ten en cuenta que las llamadas restantes de tu plan anterior no se transferirán al nuevo plan, por lo que debes considerar esto al actualizar. Se te cobrará el monto total del nuevo plan.
Para verificar cuántas llamadas a la API te quedan en el mes actual, revisa el campo 'X-Zyla-API-Calls-Monthly-Remaining' en el encabezado de la respuesta. Por ejemplo, si tu plan permite 1,000 solicitudes por mes y has usado 100, este campo mostrará 900 llamadas restantes.
Para ver el número máximo de solicitudes a la API que permite tu plan, revisa el encabezado de la respuesta 'X-Zyla-RateLimit-Limit'. Por ejemplo, si tu plan incluye 1,000 solicitudes por mes, este encabezado mostrará 1,000.
El encabezado 'X-Zyla-RateLimit-Reset' muestra el número de segundos hasta que tu límite se restablezca. Esto te indica cuándo tu conteo de solicitudes se reiniciará. Por ejemplo, si muestra 3,600, significa que faltan 3,600 segundos para que el límite se restablezca.
Sí, puedes cancelar tu plan en cualquier momento desde tu cuenta, seleccionando la opción de cancelación en la página de Facturación. Ten en cuenta que las actualizaciones, degradaciones y cancelaciones tienen efecto inmediato. Además, al cancelar ya no tendrás acceso al servicio, incluso si te quedaban llamadas en tu cuota.
Puedes contactarnos a través de nuestro canal de chat para recibir asistencia inmediata. Siempre estamos en línea de 8 a. m. a 5 p. m. (EST). Si nos contactas fuera de ese horario, te responderemos lo antes posible. Además, puedes escribirnos por correo electrónico a [email protected]
Para darte la oportunidad de probar nuestras APIs sin compromiso, ofrecemos una prueba gratuita de 7 días que te permite realizar hasta 50 llamadas a la API sin costo. Esta prueba solo se puede usar una vez, por lo que recomendamos aplicarla a la API que más te interese. Aunque la mayoría de nuestras APIs ofrecen prueba gratuita, algunas pueden no hacerlo. La prueba finaliza después de 7 días o cuando realices 50 solicitudes, lo que ocurra primero. Si alcanzas el límite de 50 solicitudes durante la prueba, deberás "Iniciar tu Plan de Pago" para continuar haciendo solicitudes. Puedes encontrar el botón "Iniciar tu Plan de Pago" en tu perfil bajo Suscripción -> Elige la API a la que estás suscrito -> Pestaña de Precios. Alternativamente, si no cancelas tu suscripción antes del día 7, tu prueba gratuita finalizará y tu plan se cobrará automáticamente, otorgándote acceso a todas las llamadas a la API especificadas en tu plan. Ten esto en cuenta para evitar cargos no deseados.
Después de 7 días, se te cobrará el monto total del plan al que estabas suscrito durante la prueba. Por lo tanto, es importante cancelar antes de que finalice el periodo de prueba. No se aceptan solicitudes de reembolso por olvidar cancelar a tiempo.
Cuando te suscribes a una prueba gratuita de una API, puedes realizar hasta 50 llamadas. Si deseas realizar más llamadas después de este límite, la API te pedirá que "Inicies tu Plan de Pago". Puedes encontrar el botón "Iniciar tu Plan de Pago" en tu perfil bajo Suscripción -> Elige la API a la que estás suscrito -> Pestaña de Precios.
Las Órdenes de Pago se procesan entre el día 20 y el 30 de cada mes. Si envías tu solicitud antes del día 20, tu pago será procesado dentro de ese período.
Nivel de Servicio:
100%
Tiempo de Respuesta:
19.514ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
2.173ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
953ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
759ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
2.073ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
712ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
1.070ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
615ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
356ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
156ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
0ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
0ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
1.211ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
2.377ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
0ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
1.054ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
0ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
0ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
5.174ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
2.310ms
Registro gratuito
