Network · data from 2026-11-12
AS269109 MARKTEC TELECOM
Registry name: AS269109 - MARKTEC TELECOM, BR · PeeringDB
4IPv4 routes
100.0% RPKI valid · 75.0% with a route object
23IPv6 routes
100.0% RPKI valid · 30.4% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
17 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
4Route objects not announced
registered with origin AS269109, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS269109, 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.
| 45.231.174.0/24 | Valid | None | 668 99% |
| 2804:5f90::/36 | Valid | Nonecovered by 2804:5f90::/34 | 633 100% |
| 2804:5f90:1000::/36 | Valid | Nonecovered by 2804:5f90::/34 | 633 100% |
| 2804:5f90:2000::/36 | Valid | Nonecovered by 2804:5f90::/34 | 633 100% |
| 2804:5f90:6000::/36 | Valid | Nonecovered by 2804:5f90:4000::/34 | 633 100% |
| 2804:5f90:9000::/36 | Valid | Nonecovered by 2804:5f90:8000::/34 | 633 100% |
| 2804:5f90:c000::/36 | Valid | Nonecovered by 2804:5f90:c000::/34 | 633 100% |
| 2804:5f90:f000::/36 | Valid | Nonecovered by 2804:5f90:c000::/34 | 633 100% |
| 2804:5f90:3000::/36 | Valid | Nonecovered by 2804:5f90::/34 | 632 99% |
| 2804:5f90:4000::/36 | Valid | Nonecovered by 2804:5f90:4000::/34 | 632 99% |
| 2804:5f90:5000::/36 | Valid | Nonecovered by 2804:5f90:4000::/34 | 632 99% |
| 2804:5f90:7000::/36 | Valid | Nonecovered by 2804:5f90:4000::/34 | 632 99% |
| 2804:5f90:8000::/36 | Valid | Nonecovered by 2804:5f90:8000::/34 | 632 99% |
| 2804:5f90:a000::/36 | Valid | Nonecovered by 2804:5f90:8000::/34 | 632 99% |
| 2804:5f90:b000::/36 | Valid | Nonecovered by 2804:5f90:8000::/34 | 632 99% |
| 2804:5f90:d000::/36 | Valid | Nonecovered by 2804:5f90:c000::/34 | 632 99% |
| 2804:5f90:e000::/36 | Valid | Nonecovered by 2804:5f90:c000::/34 | 632 99% |
| 45.179.68.0/22 | Valid | Other IRR onlyRADB, TC | 666 99% |
| 2804:5f90::/32 | Valid | Other IRR onlyRADB, TC | 633 100% |
| 2804:5f90::/34 | Valid | Other IRR onlyTC | 633 100% |
| 2804:5f90:8000::/33 | Valid | Other IRR onlyTC | 633 100% |
| 2804:5f90:8000::/34 | Valid | Other IRR onlyTC | 633 100% |
| 2804:5f90:c000::/34 | Valid | Other IRR onlyTC | 633 100% |
| 2804:5f90::/33 | Valid | Other IRR onlyTC | 630 99% |
| 2804:5f90:4000::/34 | Valid | Other IRR onlyTC | 630 99% |
| 45.179.68.0/23 | Valid | Other IRR onlyRADB, TC | 128 19% |
| 45.179.70.0/23 | Valid | Other IRR onlyRADB, TC | 128 19% |
AS-SET
PeeringDB's irr_as_set for AS269109: AS-MARKTEC-CUSTOMERS. 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 (AS269109 isn't in the set, or no route object for AS269109 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.
| Name | Database | ASNs | Sets | AS269109 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-MARKTEC-CUSTOMERS | In no IRR database read today. | |||||
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 32 are in fix.csv.
- Route object: none17
- Route object: RIR10
- AS-SET: not found1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.231.174.0/24 | No route object for it. Add a route object with origin AS269109 in the RIR database for the space. |
| Route object: none | 2804:5f90::/36 | No route object for it. A route object for 2804:5f90::/34 with origin AS269109 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269109 in the RIR database for the space. |
| Route object: none | 2804:5f90:1000::/36 | No route object for it. A route object for 2804:5f90::/34 with origin AS269109 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269109 in the RIR database for the space. |
| Route object: none | 2804:5f90:2000::/36 | No route object for it. A route object for 2804:5f90::/34 with origin AS269109 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269109 in the RIR database for the space. |
| Route object: none | 2804:5f90:6000::/36 | No route object for it. A route object for 2804:5f90:4000::/34 with origin AS269109 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269109 in the RIR database for the space. |
| Route object: none | 2804:5f90:9000::/36 | No route object for it. A route object for 2804:5f90:8000::/34 with origin AS269109 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269109 in the RIR database for the space. |
| Route object: none | 2804:5f90:c000::/36 | No route object for it. A route object for 2804:5f90:c000::/34 with origin AS269109 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269109 in the RIR database for the space. |
| Route object: none | 2804:5f90:f000::/36 | No route object for it. A route object for 2804:5f90:c000::/34 with origin AS269109 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269109 in the RIR database for the space. |
| Route object: none | 2804:5f90:3000::/36 | No route object for it. A route object for 2804:5f90::/34 with origin AS269109 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269109 in the RIR database for the space. |
| Route object: none | 2804:5f90:4000::/36 | No route object for it. A route object for 2804:5f90:4000::/34 with origin AS269109 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269109 in the RIR database for the space. |
| Route object: none | 2804:5f90:5000::/36 | No route object for it. A route object for 2804:5f90:4000::/34 with origin AS269109 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269109 in the RIR database for the space. |
| Route object: none | 2804:5f90:7000::/36 | No route object for it. A route object for 2804:5f90:4000::/34 with origin AS269109 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269109 in the RIR database for the space. |
| Route object: none | 2804:5f90:8000::/36 | No route object for it. A route object for 2804:5f90:8000::/34 with origin AS269109 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269109 in the RIR database for the space. |
| Route object: none | 2804:5f90:a000::/36 | No route object for it. A route object for 2804:5f90:8000::/34 with origin AS269109 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269109 in the RIR database for the space. |
| Route object: none | 2804:5f90:b000::/36 | No route object for it. A route object for 2804:5f90:8000::/34 with origin AS269109 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269109 in the RIR database for the space. |
| Route object: none | 2804:5f90:d000::/36 | No route object for it. A route object for 2804:5f90:c000::/34 with origin AS269109 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269109 in the RIR database for the space. |
| Route object: none | 2804:5f90:e000::/36 | No route object for it. A route object for 2804:5f90:c000::/34 with origin AS269109 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269109 in the RIR database for the space. |
| Route object: RIR | 45.179.68.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5f90::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5f90::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5f90:8000::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5f90:8000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5f90:c000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5f90::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5f90:4000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.179.68.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.179.70.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| AS-SET: not found | AS-MARKTEC-CUSTOMERS | PeeringDB names AS-MARKTEC-CUSTOMERS; no IRR database read has it. |
Route objects not announced
Route objects with origin AS269109 whose prefix no peer sees AS269109 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.179.68.0/24 | TC | Valid |
| 45.179.69.0/24 | TC | Valid |
| 45.179.70.0/24 | TC | Valid |
| 45.179.71.0/24 | TC | Valid |
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.