bgpreport

Network · data from 2026-11-12

AS153055 Tamaraw Vision Network Inc.

Registry name: TAMARAW-AS-AP - TAMARAW VISION NETWORK INC., PH · PeeringDB

2IPv4 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
0Low visibility seen by under 10% of full-table peers
26Route objects not announced registered with origin AS153055, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS153055, 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.

160.25.94.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
160.25.95.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
2401:afe0::/32 Valid RIR databaseAPNIC 636 100% 68

AS-SET

PeeringDB's irr_as_set for AS153055: APNIC::AS153055:AS-TAMARAW. 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 (AS153055 isn't in the set, or no route object for AS153055 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.

NameDatabaseASNsSets Route objectsAS153055 in itNot covered
APNIC::AS153055:AS-TAMARAW APNIC 1129 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 26 are in fix.csv.

  • Route object: not announced26

Route objects not announced

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

160.25.94.0/23APNIC, NTTCOM, RADBValid
2401:afe0::/33APNICValid
2401:afe0::/34APNICValid
2401:afe0::/35APNICValid
2401:afe0::/36APNICValid
2401:afe0:1000::/36APNICValid
2401:afe0:2000::/35APNICValid
2401:afe0:2000::/36APNICValid
2401:afe0:3000::/36APNICValid
2401:afe0:4000::/35APNICValid
2401:afe0:4000::/36APNICValid
2401:afe0:5000::/36APNICValid
2401:afe0:6000::/35APNICValid
2401:afe0:6000::/36APNICValid
2401:afe0:8000::/33APNICValid
2401:afe0:8000::/34APNICValid
2401:afe0:8000::/36APNICValid
2401:afe0:9000::/36APNICValid
2401:afe0:a000::/35APNICValid
2401:afe0:b000::/36APNICValid
2401:afe0:c000::/34APNICValid
2401:afe0:c000::/35APNICValid
2401:afe0:c000::/36APNICValid
2401:afe0:e000::/35APNICValid
2401:afe0:e000::/36APNICValid
2401:afe0:f000::/36APNICValid

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.