Network · data from 2026-11-12
AS268824 Connectmax Telecom
Registry name: AS268824 - CONNECTMAX TELECOM, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS268824, 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.172.203.0/24 | Valid | Nonecovered by 45.172.202.0/23 | 673 100% |
| 2804:5b30:ff00::/44 | Valid | Nonecovered by 2804:5b30:8000::/33 | 634 100% |
| 2804:5b30:ff30::/48 | Valid | Nonecovered by 2804:5b30:ff30::/44 | 633 100% |
| 2804:5b30:ff10::/44 | Valid | Nonecovered by 2804:5b30:8000::/33 | 629 99% |
| 45.172.200.0/24 | Valid | Other IRR onlyALTDB, TC | 673 100% |
| 45.172.201.0/24 | Valid | Other IRR onlyALTDB, TC | 673 100% |
| 45.172.202.0/24 | Valid | Other IRR onlyALTDB, TC | 673 100% |
| 45.172.200.0/22 | Valid | Other IRR onlyALTDB, RADB, TC | 672 100% |
| 179.107.55.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 179.107.52.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 179.107.54.0/24 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 179.107.53.0/24 | Valid | Other IRR onlyTC | 667 99% |
| 2804:5b30::/33 | Valid | Other IRR onlyALTDB | 636 100% |
| 2804:5b30:8000::/33 | Valid | Other IRR onlyALTDB | 636 100% |
| 2804:5b30::/32 | Valid | Other IRR onlyALTDB, RADB, TC | 634 100% |
| 2804:5b30:ff20::/44 | Valid | Other IRR onlyRADB | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS268824: AS268824:AS-CONNECTMAX. 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 (AS268824 isn't in the set, or no route object for AS268824 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 | AS268824 in it | Not covered |
|---|---|---|---|---|---|
| AS268824:AS-CONNECTMAX | TC | 3 | 1 | 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 20 are in fix.csv.
- Route object: none4
- Route object: RIR12
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.172.203.0/24 | No route object for it. A route object for 45.172.202.0/23 with origin AS268824 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268824 in the RIR database for the space. |
| Route object: none | 2804:5b30:ff00::/44 | No route object for it. A route object for 2804:5b30:8000::/33 with origin AS268824 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268824 in the RIR database for the space. |
| Route object: none | 2804:5b30:ff30::/48 | No route object for it. A route object for 2804:5b30:ff30::/44 with origin AS268824 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268824 in the RIR database for the space. |
| Route object: none | 2804:5b30:ff10::/44 | No route object for it. A route object for 2804:5b30:8000::/33 with origin AS268824 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268824 in the RIR database for the space. |
| Route object: RIR | 45.172.200.0/24 | Route object only in ALTDB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.172.201.0/24 | Route object only in ALTDB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.172.202.0/24 | Route object only in ALTDB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.172.200.0/22 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 179.107.55.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 179.107.52.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 179.107.54.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 179.107.53.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5b30::/33 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5b30:8000::/33 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5b30::/32 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5b30:ff20::/44 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS268824 whose prefix no peer sees AS268824 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.172.200.0/23 | ALTDB, TC | Valid |
| 45.172.202.0/23 | ALTDB, TC | Valid |
| 179.107.52.0/22 | RADB | Valid |
| 2804:5b30:ff30::/44 | 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.