Network · data from 2026-11-12
AS132132 MyRepublic
Registry name: REPUBLICTELECOM-SG - MyRepublic Ltd., SG · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS132132, 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.
| 2403:7f00::/35 | No ROA | Nonecovered by 2403:7f00::/32 | 636 100% |
| 2403:7f00:4000::/35 | No ROA | Nonecovered by 2403:7f00::/32 | 636 100% |
| 70.104.255.128/30 | No ROA | None | 1 0%low visibility |
| 205.158.18.10/32 | No ROA | None | 1 0%low visibility |
| 208.95.184.200/32 | No ROA | None | 1 0%low visibility |
| 66.96.222.0/24 | Valid | RIR databaseAPNIC, RADB, REACH | 673 100% |
| 101.100.187.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 673 100% |
| 101.100.191.0/24 | Valid | RIR databaseAPNIC, RADB, REACH | 673 100% |
| 103.6.148.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS132132: AS-132132-TRANSIT. 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 (AS132132 isn't in the set, or no route object for AS132132 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 | AS132132 in it | Not covered |
|---|---|---|---|---|---|
| AS-132132-TRANSIT | RADB | 31 | 1 | Yes | 3 |
| APNIC (also) | 4 | 1 | No | 9 |
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 16 are in fix.csv.
- ROA: none5
- Route object: none5
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2403:7f00::/35 | No ROA covers it. Add a ROA for AS132132, maxLength 35. |
| Route object: none | 2403:7f00::/35 | No route object for it. A route object for 2403:7f00::/32 with origin AS132132 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132132 in the RIR database for the space. |
| ROA: none | 2403:7f00:4000::/35 | No ROA covers it. Add a ROA for AS132132, maxLength 35. |
| Route object: none | 2403:7f00:4000::/35 | No route object for it. A route object for 2403:7f00::/32 with origin AS132132 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132132 in the RIR database for the space. |
| ROA: none | 70.104.255.128/30 | No ROA covers it. Add a ROA for AS132132, maxLength 30. |
| Route object: none | 70.104.255.128/30 | No route object for it. Add a route object with origin AS132132 in the RIR database for the space. |
| ROA: none | 205.158.18.10/32 | No ROA covers it. Add a ROA for AS132132, maxLength 32. |
| Route object: none | 205.158.18.10/32 | No route object for it. Add a route object with origin AS132132 in the RIR database for the space. |
| ROA: none | 208.95.184.200/32 | No ROA covers it. Add a ROA for AS132132, maxLength 32. |
| Route object: none | 208.95.184.200/32 | No route object for it. Add a route object with origin AS132132 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS132132 whose prefix no peer sees AS132132 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.241.63.133/32 | APNIC | Invalid: origin |
| 223.202.251.0/24 | NTTCOM, RADB | No ROA |
| 2402:3300::/32 | RADB | No ROA |
| 2403:3100::/32 | RADB | No ROA |
| 2403:7f00::/32 | RADB | No ROA |
| 2405:3100::/32 | RADB | No ROA |
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.