bgpreport

Network · data from 2026-11-12

AS273177 TELECOM3000 S.A.

Registry name: AS273177 - TELECOM3000 S.A., EC · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273177, 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.
148.227.173.0/24 Valid RIR databaseLACNIC, RADB 664 99% 67
193.160.220.0/24 Valid RIR databaseRADB, RIPE 664 99% 67
2803:ca50::/32 Valid RIR databaseLACNIC, RADB 633 100% 67
2803:ca50:1c01::/48 Valid RIR databaseLACNIC 633 100% 67
2803:ca50:1c02::/48 Valid RIR databaseLACNIC 633 100% 67
2803:ca50:1f01::/48 Valid RIR databaseLACNIC 633 100% 67
2803:ca50:1f02::/48 Valid RIR databaseLACNIC 633 100% 67
2803:ca50:2c01::/48 Valid RIR databaseLACNIC 633 100% 67
2803:ca50:2c02::/48 Valid RIR databaseLACNIC 633 100% 67
2803:ca50:2f01::/48 Valid RIR databaseLACNIC 633 100% 67
2803:ca50:2f02::/48 Valid RIR databaseLACNIC 633 100% 67
2803:ca50:3c00::/48 Valid RIR databaseLACNIC 633 100% 67
2803:ca50:3f00::/48 Valid RIR databaseLACNIC 633 100% 67
2803:ca50:4c01::/48 Valid RIR databaseLACNIC 633 100% 67
2803:ca50:4f01::/48 Valid RIR databaseLACNIC 633 100% 67
2803:ca50:bac1::/48 Valid RIR databaseLACNIC 633 100% 67
2803:ca50:eee0::/48 Valid RIR databaseLACNIC 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS273177: AS273177. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS273177 isn't in the set, or no route object for AS273177 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS273177 in itNot covered
AS273177 A single AS number, not a set: AS273177 (this network), 17 route objects.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS273177 is announced.

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.