Network · data from 2026-11-12
AS139780 BIC-AS-AP - Brother's ICT Connectivity
Registry name: BIC-AS-AP - Brother's ICT Connectivity, BD · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS139780, 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.
| 103.225.219.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 103.154.17.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 160.250.9.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.145.45.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.145.44.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.145.44.0/23 | Valid | RIR databaseAPNIC | 44 7%low visibility |
AS-SET
AS139780 isn't in PeeringDB, where networks name their AS-SET.
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 3 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.225.219.0/24 | ROAs covering it name AS137868, not AS139780. If AS139780 should announce it, add a ROA for AS139780. |
| Route object: none | 103.225.219.0/24 | Route objects for it name AS137868. Add a route object with origin AS139780 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS139780 whose prefix no peer sees AS139780 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:df1:f780::/48 | APNIC | 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.