Primary audience
Natural-gas traders, utilities, marketers, shippers, pipeline schedulers, basis analysts, and operations teams monitoring constraints and maintenance.
Energy data research
Experiment 4 · EBB notice preservation
Natural gas pipeline notice archives: a transience experiment
Can repeated captures of public pipeline EBBs preserve critical notices, planned service outages, revisions, and cancellations well enough to create a normalized historical record?
Status
collection probe
Initial scope
ANR Pipeline, Natural Gas Pipeline Company of America, and Transco public EBB surfaces
Collection cadence
Five-to-fifteen-minute polling during the probe, with immutable versions and explicit failures
Last reviewed
2026-08-11
This is not a live pipeline-capacity product, operational alert service, or production archive. It is a public-source collection experiment.
Decision context
What this experiment must decide
Decision question
Are public EBB notices transient and heterogeneous enough—and buyer-relevant enough—to justify continuous capture and cross-pipeline normalization?
Why collect now
Pipeline notices may be revised, replaced, or exposed only through short lookback windows. Every day without collection can permanently reduce the history available for a future product decision.
P · Problem
Problem
Interstate pipeline EBBs publish critical notices, non-critical notices, maintenance, planned service outages, operational alerts, and other shipper information. The categories, identifiers, lookback behavior, page structure, and revision practices differ by operator.
A notice can matter to a basis trader or scheduler before it appears in a clean third-party dataset. Yet a notice index is not the same as real-time capacity, nominations, or confirmed market impact. A responsible archive must preserve the operator’s words and timestamps without inventing severity or flow effects.
The source may expose only a recent window. NGPL’s public critical-notice screen states that notices ninety days before the selected date are displayed. That creates a concrete transience hypothesis: continuous collection may retain history that a later visitor cannot recover from the default interface.
A · Approach
Approach
The collection design is intentionally narrower than a production data platform. It preserves evidence, makes uncertainty explicit, and produces a measurable build/no-build decision.
- 1
Register each EBB surface
Record operator, TSP identifier, notice categories, public URLs, query controls, time zone, lookback behavior, terms, and technical dependencies.
- 2
Poll indexes conservatively
Use a clear user agent, bounded frequency, timeout, and response-size limit. Stop on blocking or terms concerns rather than bypassing controls.
- 3
Preserve notices and attachments
Store index responses, detail pages, downloads, response headers, retrieval timestamps, and hashes as immutable artifacts.
- 4
Model revisions explicitly
Use operator notice IDs and source evidence to connect updates, cancellations, supersessions, and changing end dates. Do not assume a changed page is a new event.
- 5
Normalize a minimal taxonomy
Map source categories only where defensible: critical, non-critical, maintenance, planned outage, force majeure, operational flow order, capacity-affecting, or unclassified.
- 6
Validate commercial signal
Ask schedulers and traders which notices change a workflow, then compare high-value notice rate with collection and review cost.
R · Research
Research
These are current findings and their decision implications. They are not promises about future OilPriceAPI coverage.
| Issue | Observed finding | Decision implication |
|---|---|---|
| Public categories are real but heterogeneous | ANR’s public navigation lists critical, non-critical, planned service outage, and notice search functions. | Category mapping can start with operator labels, but a cross-pipeline severity ontology requires observed examples and buyer review. |
| Lookback can be limited | NGPL’s critical-notice screen says notices ninety days before the selected date will be displayed. | Immutable capture may create recoverable history, but the collector must test query controls before claiming older notices are unavailable. |
| Notice fields can support structured records | NGPL exposes notice type, post time, effective time, end time, notice ID, subject, and whether a notice affects capacity. | A minimal normalized schema is plausible without interpreting the full text automatically. |
| Transco separates major notice families | The Transco 1Line site map lists critical, non-critical, and planned service outage sections. | A collector can begin from public navigation, but detail and archive endpoints must be tested for stable access. |
| Commercial aggregation already exists | The research scan found NatGasHub, Capacity Center, Enercast, and S&P Global offerings built around pipeline information and alerts. | Buyer demand has precedent; differentiation must come from coverage, history, reliability, provenance, or workflow—not merely mirroring an index page. |
M · Measurement
Measurement
Primary decision metric
Unique buyer-relevant notice versions preserved beyond default source visibility per supported pipeline, divided by monthly collection and review cost.
Polling reliability
Successful expected responses divided by scheduled attempts, with blocks reported separately.
Notice yield
New notice IDs and meaningful revisions per pipeline per day.
Revision rate
Notices whose text, timing, status, or attachments change after first capture.
Transience yield
Artifacts retained by the collector that later leave the tested public view.
Field completeness
Records with operator, source ID, type, post/effective/end time, subject, and evidence.
Classification agreement
Agreement between normalized labels and buyer/analyst review.
High-value notice rate
Collected notices buyers mark workflow-relevant divided by reviewed notices.
Onboarding cost
Engineering hours to add and stabilize one new pipeline.
Continue when
- ✓At least five buyer-priority pipelines can be polled reliably without bypassing access controls or violating documented restrictions.
- ✓The probe preserves revisions or expired/default-hidden notices that are useful to at least three target users.
- ✓Normalized core fields reach at least 95% audited accuracy while preserving raw operator text and source timestamps.
Stop or redesign when
- ×Public access, terms, or unstable anti-automation behavior prevents reliable lawful collection of buyer-priority pipelines.
- ×Most captured notices are noise for target workflows and filtering requires uneconomic continuous analyst review.
Initial collection
Started
2026-08-11T21:35:40Z
Current status
NGPL and Transco returned HTTP 200; ANR failed at the transport layer in the first bounded capture.
Baseline observations
- •The ANR URL is an official public notice surface, but the first automated HTTPS request returned only a transport-level fetch failure; no availability claim is made from that attempt.
- •NGPL exposes structured critical-notice fields and states a ninety-day display window relative to the selected date.
- •Transco 1Line separates critical, non-critical, and planned service outage navigation.
- •A successful baseline proves point-in-time accessibility only; the ANR failure also shows why source reliability must be measured separately from notice coverage.
Next capture
Poll the three baseline indexes conservatively, add two buyer-priority pipelines, and retain every changed version for fourteen days.
Proposed record schema
The schema is a test contract, not a public endpoint specification. Unknown values remain unknown, and every derived field must retain source evidence.
- pipeline
- Canonical operator and TSP identity.
- notice_id
- Operator-provided identifier, not a generated replacement.
- source_notice_type
- The operator’s original category label.
- normalized_type
- Conservative mapped category, including unclassified.
- posted_at
- Operator post time with source time zone.
- effective_start/end
- Stated operational window; unknown remains unknown.
- revision_of
- Prior version or notice only where source evidence supports the link.
- source_hash
- Hash of each retained page or attachment version.
Sources and scope
OilPriceAPI Research prepared this page to test a product decision. The method combines direct-source review, immutable collection probes, and explicit decision gates. External links establish what each source publishes; they do not grant OilPriceAPI redistribution rights or prove complete coverage.
ANR EBB notice navigation
ANR Pipeline Company
Supports: Public notice families including critical, non-critical, and planned service outages.
Limitation: Navigation presence does not prove every detail or archive endpoint supports stable automated retrieval.
NGPL critical notices
Natural Gas Pipeline Company of America
Supports: Structured notice fields and the stated ninety-day display behavior.
Limitation: The tested interface and its query controls may change; capacity impact must not be inferred from subject text alone.
Transco informational-postings site map
Williams / Transcontinental Gas Pipe Line Company
Supports: Official public navigation for critical, non-critical, and planned service outage notices.
Limitation: The site map is a discovery surface, not itself a complete notice archive.
Help validate the next decision
If this dataset is part of your workflow, tell us which sources matter, what failure looks like, and what evidence would make the data useful enough to buy. A conversation is evidence; a page view is not.