bgpreport

Network · data from 2026-11-12

AS266673 FLYTEC TELECOM SOCIEDAD ANONIMA

Registry name: AS266673 - FLYTEC TELECOM SOCIEDAD ANONIMA, PY · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266673, 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.
2803:8920:6000::/36 Valid Nonecovered by 2803:8920::/32 635 100% 67
45.228.136.0/23 Valid Other IRR onlyRADB 669 99% 67
45.228.138.0/23 Valid Other IRR onlyRADB 669 99% 67
45.228.137.0/24 Valid Other IRR onlyRADB 668 99% 67
45.228.138.0/24 Valid Other IRR onlyRADB 668 99% 67
45.228.136.0/24 Valid Other IRR onlyRADB 667 99% 67
45.228.139.0/24 Valid Other IRR onlyRADB 667 99% 67
45.228.136.0/22 Valid RIR databaseLACNIC, RADB 669 99% 67
2803:8920::/32 Valid RIR databaseLACNIC 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS266673: AS262567:AS-CONE. 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 (AS266673 isn't in the set, or no route object for AS266673 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 objectsAS266673 in itNot covered
AS262567:AS-CONE RADB 4126 Yes 0

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 7 are in fix.csv.

  • Route object: none1
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: none2803:8920:6000::/36No route object for it. A route object for 2803:8920::/32 with origin AS266673 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266673 in the RIR database for the space.635 of 636
Route object: RIR45.228.136.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR45.228.138.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR45.228.137.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR45.228.138.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR45.228.136.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR45.228.139.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

Every route object with origin AS266673 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.