bgpreport

Network · data from 2026-11-12

AS136267 INFO-INTERNET-AS-AP - Info Internet Service

Registry name: INFO-INTERNET-AS-AP - Info Internet Service, BD · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136267, 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.85.196.0/24 Valid RIR databaseAPNIC 673 100% 67
103.85.197.0/24 Valid RIR databaseAPNIC 673 100% 70
103.85.198.0/24 Valid RIR databaseAPNIC 673 100% 67
103.85.199.0/24 Valid RIR databaseAPNIC 673 100% 67
2400:afc0::/32 Valid RIR databaseAPNIC 0 0%low visibility 1

AS-SET

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

  • Route object: not announced7

Route objects not announced

Route objects with origin AS136267 whose prefix no peer sees AS136267 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.85.196.0/22APNICValid
103.85.196.0/23APNICValid
103.85.198.0/23APNICValid
2400:afc0:196::/48APNICValid
2400:afc0:197::/48APNICValid
2400:afc0:198::/48APNICValid
2400:afc0:199::/48APNICValid

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.